Comments
Sort by recent activity
Embedded assemblies have no useful location to tell you. They aren't decompressed to a temporary location or anything, they are simply loaded from memory. / comments
Embedded assemblies have no useful location to tell you. They aren't decompressed to a temporary location or anything, they are simply loaded from memory.
Thanks for the information, we'll be asking people about that if anyone else has similar inexplicable problems with MSBuild. / comments
Thanks for the information, we'll be asking people about that if anyone else has similar inexplicable problems with MSBuild.
No, sorry, there's no logging that would be useful here.
There's no assembly in the GAC that might have any effect here. / comments
No, sorry, there's no logging that would be useful here.
There's no assembly in the GAC that might have any effect here.
SmartAssembly.MSBuild.Tasks.dll lives in the GAC and should have a file version of whichever build you have installed (5.5.0.153) but an assembly version of 5.0.0.0
If it got as far as giving the error about the database connection, all assemblies must have loaded fine. / comments
SmartAssembly.MSBuild.Tasks.dll lives in the GAC and should have a file version of whichever build you have installed (5.5.0.153) but an assembly version of 5.0.0.0
If it got as far as giving the e...
Hia,
It's interesting, we improved the handling of the database connection dropping out in 5.5, so that it was meant to reconnect correctly.
But I think you're saying that this happens reliably, which suggests that perhaps something is actively closing the database connection. You're using it from an MSBuild task, perhaps you're invoking SA twice, and some kind of timeout is happening in between times? Using SA twice from one MSBuild process will reuse the database connection.
Perhaps a timeout can be configured at your SQL server. If not, perhaps switching to using the command line from an MSBuild Exec task may work, as then a completely separate instance of SA is used, which will have a separate database connection, so can't time out.
Hope that helps, / comments
Hia,
It's interesting, we improved the handling of the database connection dropping out in 5.5, so that it was meant to reconnect correctly.
But I think you're saying that this happens reliably, wh...
I'm afraid I can't think of any other reasons it might happen, and without being able to reproduce it in the main UI to get a better error message, I can't help further.
I suggest you work around it by using the command line tool and the Exec MSBuild task
<Target Name="AfterCompile">
<Exec Command="C:\Program Files\Red Gate\SmartAssembly 5\SmartAssembly.com MyApplication.saproj" />
</Target>
/ comments
I'm afraid I can't think of any other reasons it might happen, and without being able to reproduce it in the main UI to get a better error message, I can't help further.
I suggest you work around i...
Interesting. When you say the latest build, do you mean the 5.5 EAP, or 5.1? / comments
Interesting. When you say the latest build, do you mean the 5.5 EAP, or 5.1?
Hi cadi
There are ways to use different settings files, but let's see if we can solve your root problem first...
The Silverlight SDK folders you're talking about should be searched automatically by SmartAssembly. Which one is searched depends on which version of Silverlight your app targets (via the TargetFrameworkAttribute).
Also, if you want something per-project, you could always use the HintPath in the saproj file. I know it means doing something for each assembly though. / comments
Hi cadi
There are ways to use different settings files, but let's see if we can solve your root problem first...
The Silverlight SDK folders you're talking about should be searched automatically by...
You can work out whether this is the case by taking a second snapshot. Doing that tends to run all the finalizers and clear up any objects that are only held by the finalizer queue. / comments
You can work out whether this is the case by taking a second snapshot. Doing that tends to run all the finalizers and clear up any objects that are only held by the finalizer queue.
In the same way as reflection, use of the dynamic keyword in c# doesn't mix well with obfuscation.
The only options, as you say, are:
- excluding the affected method from obfuscation
- avoiding calling obfuscatable methods on the dynamic variables
I don't believe it's possible for any obfuscator to allow you to use dynamic variables. / comments
In the same way as reflection, use of the dynamic keyword in c# doesn't mix well with obfuscation.
The only options, as you say, are:
- excluding the affected method from obfuscation
- avoiding cal...