I\'ve been rather confused by some SGEN stuff. I\'ve enable the generation of serialization assemblies for one of my projects. Originally I got the follow error which I believe I\'ve solved by doing s
I must be going mental, right? Since a couple of days I have been getting errors like MyAssemblyCould not load file or assembly \'AnotherAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=\
Logged into a customer environment today to check logs and just generally do an inspection, only to notice some tasks had failed in one application.
I ran into problems when trying to xml serialize a class to xml after I changed it from public to internal. Before I changed protection level it was working fine, so I am looking for a way to get arou
I came across some strange behavior with the SGEN tool that is used to generate classes from SGEN\'s.
I have a sgen step in my .NET 3.5 library, producing a correct XYZ.XmlSerializers.dll in the output directory.
My .NET assembly is signed with digital certificate from comodo. I use SGEN to generate serialization assembly. SGEN requires a key file in order to generate such assembly for a signed source. I tried
Our dev team recently upgraded solution to VS2010 from VS2008 to use some of the features from VS2010 IDE. But our targeted framework is still .Net 3.5. When dev runs the MSBuild from VS 2008 command
I\'m getting this error in my WPF application. I get this error not always. If I make Clean and then Rebuild everything is ok.
So I\'m trying to speed up our applications startup times -- and I\'ve identified a major bottleneck to work on.Each of our webservice client classes takes forever and a day to instantiate.Some invest
加载中,请稍侯......