Activity overview
Latest activity by toma
As you see in my first post I already tried that, and it did not work.
Seemed like SA ignores the DependencySearchPath in the settings file if the "correct" assembly is already found in the GAC...? / comments
As you see in my first post I already tried that, and it did not work.
Seemed like SA ignores the DependencySearchPath in the settings file if the "correct" assembly is already found in the GAC...?
I solved this myself.
Seems like .NET Framework 4 Beta 1 put dll's in the same GAC as .NET Framework 3.5 and those was not removed when I installed the released version of .NET Framework 4. I was not able to remove the extra (Beta 1 marked as v4) assemblies through windows explorer, gacutil.exe or GACBrowser. The extra assemblies was not removed when I uninstalled .NET Framework 3.5 either.
Found in the end that I through the "Add references" - dialog under the browse tab in Visual Studio could access and delete the extra Beta 1 assemblies. When all of them was gone SmartAssembly picked the correct assembly and worked as intended.
kind regards
Tonny / comments
I solved this myself.
Seems like .NET Framework 4 Beta 1 put dll's in the same GAC as .NET Framework 3.5 and those was not removed when I installed the released version of .NET Framework 4. I was n...
Not able to point SA to the correct assembly
Hi
I get an errormessage:
SmartAssembly has encountered an invalid symbol in xxx
[System.ComponentModel.DataAnnotations]
System.ComponentModel.DataAnnotations.EditableAttribute
The most likely caus...