How can we help you today? How can we help you today?
DanielRose
With Windows 10 and .NET 4.6 being out, a small update for SmartAssembly to correctly recognize them in feature usage reporting would be nice [image] / comments
With Windows 10 and .NET 4.6 being out, a small update for SmartAssembly to correctly recognize them in feature usage reporting would be nice
0 votes
I have over 42000 samap files, of which I only need a couple hundred. With that amount of files, any manual search and delete won't work in any reasonable amount of time. So please add me to the list of people who could really use such a tool! / comments
I have over 42000 samap files, of which I only need a couple hundred. With that amount of files, any manual search and delete won't work in any reasonable amount of time. So please add me to the li...
0 votes
I encountered the same problem. I upgraded from .NET 4.0 to .NET 4.5.2. Even with the MandatoryPath set, I can't get it to work. The reason is that some assembly is referring to .NET 2.0: 2014-10-16 16:09:02,642 DEBUG SmartAssembly.AssemblyReader: Resolved assembly {mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e} to C:Program Files (x86)Reference AssembliesMicrosoftFramework.NETFrameworkv4.5mscorlib.dll 2014-10-16 16:09:08,401 DEBUG SmartAssembly.AssemblyReader: Using {mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089} in preference to {mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089} [mscorlib]System.Runtime.InteropServices.Marshal::StructureToPtr System.Void(!!0, System.IntPtr, System.Boolean) The most likely cause is that SmartAssembly has used a different version of a dependency from the version used by EXAPTplus.Core.dll. If the details below are wrong, please use the MandatoryPath attribute in the .saproj file to ensure that the correct version of the dependency is found. Assembly that should contain the missing symbol: C:Program Files (x86)Reference AssembliesMicrosoftFramework.NETFrameworkv4.5mscorlib.dll SmartAssembly.InformationException: SmartAssembly has encountered an invalid symbol: [mscorlib]System.Runtime.InteropServices.Marshal::StructureToPtr System.Void(!!0, System.IntPtr, System.Boolean) The most likely cause is that SmartAssembly has used a different version of a dependency from the version used by EXAPTplus.Core.dll. If the details below are wrong, please use the MandatoryPath attribute in the .saproj file to ensure that the correct version of the dependency is found. Assembly that should contain the missing symbol: C:Program Files (x86)Reference AssembliesMicrosoftFramework.NETFrameworkv4.5mscorlib.dll In the .saproj: <Assembly AssemblyName="mscorlib, Culture=neutral, PublicKeyToken=b77a5c561934e089" MandatoryPath="C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll" > <Merging /> </Assembly> / comments
I encountered the same problem. I upgraded from .NET 4.0 to .NET 4.5.2. Even with the MandatoryPath set, I can't get it to work. The reason is that some assembly is referring to .NET 2.0: 2014-10-1...
0 votes