User profile for spammenao252

I am indeed using v6.7, thanks [image] / comments

I am indeed using v6.7, thanks

0 votes

Brian Donahue wrote: I don't think SA works with PostSharp... http://www.sharpcrafters.com/blog/post/ ... or%29.aspx That's incorrect. http://www.sharpcrafters.com/blog/post/SmartAssembly-now-supports-PostSharp.aspx And also: http://www.red-gate.com/SupportCenter/content/SmartAssembly/articles/version_6xx_SmartAssembly which states: We have also improved support for Windows Phone 7.1 and Windows Phone 7.5, SQL CLR assemblies and assemblies using PostSharp. Brian Donahue wrote: But we have some information that it *may* work if you use PostSharp before you use SmartAssembly. I guess you can give that a try. But that's what I'm already doing. I'm compiling the library with Postsharp enabled, I then obfuscate that library and reference it from the main assembly (Caller) which doesn't use PostSharp at all. Weirdest of all is that it works fine if I compile the Caller using the non-obfuscated library, and then swap that dll file out with the obfuscated version. This means it's an issue with compiling using an obfuscated library rather than an issue with the library itself. There seems to be something about the SA + PostSharp combo that makes the Caller mess up constants in the library at compile time. / comments

Brian Donahue wrote: I don't think SA works with PostSharp...http://www.sharpcrafters.com/blog/post/ ... or%29.aspx That's incorrect. http://www.sharpcrafters.com/blog/post/SmartAssembly-now-s...

0 votes

I narrowed the issue down to PostSharp. Even when PostSharp doesn't alter any code, running SA after it will cause the issue. You can download a concise example of it here: https://bitbucket.org/spammenao252/smartacharerror/get/master.zip I included both a VS2010 and a VS2012 project. It occurs with both, even after setting obfuscation support to true in vs2010. Again, it occurs even if PostSharp doesn't actually do anything... the example above illustrates this. UPDATE: According to dotPeek the non-obfuscated assembly also has the questionmark-icons even if PostSharp didn't handle the assembly (though it doesn't if the postsharp library is removed entirely). Regardless, the issue does not occur if I build the Caller referencing said assembly. It also doesn't happen if I obfuscate that assembly, only PostSharp (with an un-used aspect) + SmartAssembly makes it occur. Not sure what it is that SA does that makes the Caller mess up. UPDATE 2: Ok, possibly even more interesting, if I first compile the Caller using the obfuscated version of the library that is not handled by PostSharp, and then swap that library out with the Obfuscated+PostSharp handled version, the program runs fine. But when I compile the Caller using the latter library as a direct reference, and then swap it out with the former, it still crashes. Note that the Caller doesn't have any PostSharp code and isn't handled by it at all, and that I'm also not obfuscating the Caller. How weird is this!? To summarize Does not occur when: -Compile Caller with reference to library that has PostSharp Reference -Compile Caller with reference to library that has PostSharp Reference + Aspect -Compile with either of those 2 and then swap the library with their obfuscated versions. Does occur when: -Compile Caller with reference to library that has PostSharp Reference + Obfuscation -Compile Caller with reference to library that has PostSharp Reference + Aspect + Obfuscation -Compile with either of those 2 and then swap the library with their non-obfuscated versions. Also does not occur when PostSharp reference is removed entirely and the library is then obfuscated and used for compiling the Caller (as expected ofc) / comments

I narrowed the issue down to PostSharp. Even when PostSharp doesn't alter any code, running SA after it will cause the issue. You can download a concise example of it here:https://bitbucket.org/spa...

0 votes

Thanks for checking that out. I guess I'll keep implementing workarounds whenever I bump into issues using Poshsharp, for now [image] / comments

Thanks for checking that out. I guess I'll keep implementing workarounds whenever I bump into issues using Poshsharp, for now

0 votes

Library returns weird character

I excluded the class causing the issue from obfuscation (entire namespace to be exact), but whenever the code is called from outside of the library a strange character is still appended. The classp...

2 followers 6 comments 0 votes

I narrowed the problem down to this: [SomeAspect("SomeName", "SomeString", typeof(CSomeClass))] Getting rid of the typeof() 'fixes' the issue so I guess I'll do that and implement a workaround that doesn't make my app crash after obfuscation. Regardless, can someone please elaborate on how I can properly make PostSharp and SA work together? What do I do with afformentioned .pssym file? Is it auto-used when configuring MSBuild, or? And what happens then when we build using the regular SA application to obfuscate? Or are there additional steps required to use the files either way? / comments

I narrowed the problem down to this:[SomeAspect("SomeName", "SomeString", typeof(CSomeClass))] Getting rid of the typeof() 'fixes' the issue so I guess I'll do that and im...

0 votes

I now also tried using msbuild to see what that did, but still no dice.. library ends up obfuscated as expected but program still crashes with a 'The type initializer for ' ' threw an exception.' exception. The .csproj config: <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" /> <UsingTask TaskName="SmartAssembly.MSBuild.Tasks.Build" AssemblyName="SmartAssembly.MSBuild.Tasks, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7f465a1c156d4d57" /> <Target Name="AfterBuild" Condition=" '$(Configuration)' == 'Release' "> <SmartAssembly.MSBuild.Tasks.Build ProjectFile="C:\Users\Admin\Documents\Visual Studio 2010\Projects\SmartAssFuscate\SmartAssFuscate\bin\Release\SmartAssFuscate.saproj" /> </Target> / comments

I now also tried using msbuild to see what that did, but still no dice.. library ends up obfuscated as expected but program still crashes with a 'The type initializer for ' ' threw an exception.' e...

0 votes

Can't get postsharp working

According to http://www.sharpcrafters.com/blog/post/SmartAssembly-now-supports-PostSharp.aspx SA supports postsharp since v6.6.4 and your release notes confirm this. I selected the Support for Obfu...

3 followers 7 comments 0 votes

How can we help you today?

spammenao252

Activity overview