Comments
Sort by recent activity
Apparently the 64 bit version will only work from the command line and if you are storing your reports on an SQL server. I've had no issues with it with this set up. / comments
Apparently the 64 bit version will only work from the command line and if you are storing your reports on an SQL server. I've had no issues with it with this set up.
Thanks Alex. I'll give it a go. / comments
Thanks Alex. I'll give it a go.
I've been able to authenticode sign the assemblies post obfuscation as part of the build process. Using msbuild, my csproj looks like: <Target Name="AfterCompile">
<Exec Command="$(SmartAssemblyLocation) /build $(SmartAssemblyProjectLocation)" />
<Copy SourceFiles="$(OutputPath)$(TargetFileName)" DestinationFiles="$(IntermediateOutputPath)$(TargetFileName)" />
<Exec Command=""signtool.exe" sign /t http://timestamp.server.com /i CertName "$(IntermediateOutputPath)$(TargetFileName)"" />
</Target>
/ comments
I've been able to authenticode sign the assemblies post obfuscation as part of the build process. Using msbuild, my csproj looks like:<Target Name="AfterCompile">
<Exec Command="$(Sma...
Smart assembly can be used with ClickOnce. You need to run the obfuscation in the middle of the build process. There are instructions located here. / comments
Smart assembly can be used with ClickOnce. You need to run the obfuscation in the middle of the build process. There are instructions located here.
Thanks for looking at this for us. Do you have any idea on when I could expect a new version to be released?
Thanks,
Craig / comments
Thanks for looking at this for us. Do you have any idea on when I could expect a new version to be released?
Thanks,
Craig
We send our error reports to different email address which are all forwarded to our developers. e.g. Our beta program sends errors to beta.programname.errors@company.com and production to programname.errors@company.com. They all redirect to errors@company.com, but we can see who the email was originally sent to. You could also change the product name if you want the errors to be grouped differently within the Smart Assembly error repository. / comments
We send our error reports to different email address which are all forwarded to our developers. e.g. Our beta program sends errors to beta.programname.errors@company.com and production to programn...
Hi.
It's the same issue as discussed here. I'm still waiting for a fix for this too. / comments
Hi.
It's the same issue as discussed here. I'm still waiting for a fix for this too.
Just reset all of the settings and it seems to be working now. I'd be happy to see the RunOnException functionality in a future version.
Thanks for your help. / comments
Just reset all of the settings and it seems to be working now. I'd be happy to see the RunOnException functionality in a future version.
Thanks for your help.
Funny thing is, I'm also referencing DevExpress in my program. I've managed to get SmartAssembly working by building against .Net 3.5.
Glad you guys found out what was happening. Looking forward to the next release. / comments
Funny thing is, I'm also referencing DevExpress in my program. I've managed to get SmartAssembly working by building against .Net 3.5.
Glad you guys found out what was happening. Looking forward ...
Yes, it is referencing mscorlib twice.
// Assembly Reference mscorlib
Version: 2.0.0.0
Name: mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
// Assembly Reference mscorlib
Version: 4.0.0.0
Name: mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 / comments
Yes, it is referencing mscorlib twice.
// Assembly Reference mscorlib
Version: 2.0.0.0
Name: mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
// Assembly Reference mscorl...