Hi
I started a thread on MSDN because I couldn't work out why I was getting the following error in Visual Studio 2010/2012 (Windows 7 x64) when working with all types of projects and .NET 4.0.
http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/9b8782c9-8fd4-484c-929f-9c8820765bc0/
It turns out to be caused by installing: CSLA.NET 4.5.10
Is there anything I should know about using this version on Windows 7 and with VS?
Many thanks
Andrew
You probably need to install Microsoft.CompilerServices.AsyncTargetingPack package from NuGet to enable async/await in .NET 4 and SL5 projects.
We have only used VS2012 for development so I would suggest you stay with VS2012 and target .NET 4 projects from this version.
Did you install the CSLA packages from NuGet?
Hi JonnyBee
Just to be clear - after installing CSLA 4.5, any new .NET v4.0 project in VS 2010 and VS2012, without references to any CSLA assemblies, will display the error dialog mentioned. One wouldn't expect CSLA to have an effect on the VS environment without at least being referenced in the projects.
I would probably only want to use CSLA 4.5 in a .NET Framework 4.5 project so wouldn't expect to need the Microsoft.CompilerServices.AsyncTargetingPack.
Also, according to the web site the pack cannot be used in VS2010 which probably means we'd still get the error even if we install the pack.
Can you explain why the CSLA installer affects the VS environment?
Thanks
Andrew
Did you install CSLA 4.5 using the installer from the download page?
(I have only used the NuGet installer to install into the solution only - and have not looked into the CSLA Installer code so I don't know what is installed and how) .
So what I can do is to create an issue in the CSLA Bugtracker and have someone look into it.
http://www.lhotka.net/cslabugs/edit_bug.aspx?id=1121
Hi
Yes I downloaded from here:
http://www.lhotka.net/files/csla40/Csla-4.5.10.exe
I also meet the same problem. when uninstall the Csla. the problem disappear.
According to: http://msdn.microsoft.com/en-us/library/windows/desktop/hh802935(v=vs.85).aspx
This library is windows 8 specific / does not exists in windows 7.
I uninstalled CSLA 4.5.10 from my Add/Remove programs. This fixed the problem for me.
Thanks Simon for the suggestion.
Gilles
I can also confirm this issue is caused by the CSLA 4.5.10 installer, with same fix to uninstall via Add/remove programs. I'm using Windows 7/VS2012
I just copied the files from the Program Files directory before uninstalling.
Peran
This must be a bug in InstallShield. CSLA doesn't install anything outside its own folder, but you are saying this is a global issue on your machine right? That makes me think InstallShield must be putting something into some global location - presumably something it needs, and not part of CSLA itself.
I'm experiencing the same error when I run console F# in VS2012 with csla 4.5.4. It happens when aimed at Net Framework 4.5, but I can get rid of the error by using NET 4 and referencing the appropriate CSLA dll. I don't need to uninstall 4.5.4.
VS2012 will not error if using .NET 4.0
VS2010 will error if using .NET 4.0
In both versions of VS, the program continues after the error.
I used Gilles' approach copying the CSLA.NET directory, uninstalled CSLA.NET and then recopied the directories back to the Program Files. I am now running without error on 4.5. NuGet seems to work also so it does appear to be Installshield related.
Weird!
Also, according to the web site the pack cannot be used in VS2010 which probably means we'd still get the error even if we install the pack.
I also read on MS web site that the AsyncTargetPack is for VS 2012 only. That's not true. It runs on VS2010 without any issue. There are several CSLA samples for VS2010 that target .NET 4.0 and use the AsyncTargetPack.
<edit>
Just to make it clear, the referred samples target Csla 4.5 and .NET 4.0.
</edit>
You know, I'm pretty sure this heap dll is mentioned in this occasional dialog that pops up, like you say, on all types of projects. If it's different (when I see it next time) I'll edit my post. But this started happening to me when I upgraded SL, CSLA, etc.
I'm not sure it's b/c of CSLA though, but I saw your other post on another forum where you say uninstalling CSLA 4.5 makes it go away.
I had the same issue. I installed CSLA.NET which I downloaded from lhotka.net. I uninstalled it and the problem went away.
Hi
I had the same issue, did you solve the problem?
Fwiw, I have a colleague who is working on a WiX based replacement for the current InatallShield installer. Hopefully that will eliminate this issue. The only thing I can think of is that the InstallShield setup program installs some system dll that it shouldn't. The actual Csla installation is completely contained in its own Program Files folder,, so I can't see how that would affect general VS behavior... With luck WiX won't behave like InstallShield.
Hi just got this error too.
Windows 7 64 bit.
Once CSLA 4.5 is installed the error occurs on many programs that I try to run.
If it is Installshield, by now there must be some updates. Could you rebuild 4.5 so I can try again.
thanks
In the short term I recommend installing via nuget because that doesn't have the issue.
The plan is to abandon InstallShield and switch to WiX. A colleague from Magenic has a preliminary WiX installer, I just need to get time to test it and get it worked into my release build process.
Copyright (c) Marimer LLC