Comments
Sort by recent activity
If I would use SQL server that would be no problem, but I am NOT. SA is using its own local database.
Yes, SA is invoked from a MS Build task, but it doesn't even complete the first run successfully, so there in no explanation why the connection would be closed as it doesn't even open one.
Edit: even if only one assembly is processed in the MSbuild task the same error occurs. / comments
If I would use SQL server that would be no problem, but I am NOT. SA is using its own local database.
Yes, SA is invoked from a MS Build task, but it doesn't even complete the first run successfull...
That's not too pleasing. Aren't there any extra/hidden logging features that I might turn on?
What amazes me is that I don't see it even trying to access the database file, so SQLite seems to throw the error for some unknown reason. There are no file accesses to the database ever when run in the MSBuild task. Yet the GUI or commandline works just fine.
Might this be related to some assembly in the GAC? Maybe the build task loads some assembly it should not, or it doesn't at all? / comments
That's not too pleasing. Aren't there any extra/hidden logging features that I might turn on?
What amazes me is that I don't see it even trying to access the database file, so SQLite seems to throw...
Am now back to the same problem. Can you give me ANY hint what might cause this? For the moment I am unable to do any release builds because of this slight problem. / comments
Am now back to the same problem. Can you give me ANY hint what might cause this? For the moment I am unable to do any release builds because of this slight problem.
Still trying to make it work, to no avail yet.
Some more details:
Tracing it with procmon, I see accesses to C:\Program Files\Red Gate\SmartAssembly 5\FSharp\Windows
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Test
C:\Program Files\Red Gate\SmartAssembly 5\Modeling
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Windows
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Web
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Workflow
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Cloud
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Reporting
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Silverlight
C:\Program Files\Red Gate\SmartAssembly 5\FSharp\Silverlight
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Office\Version2007
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\Office\Version2010
C:\Program Files\Red Gate\SmartAssembly 5\CSharp\WCF
C:\Program Files\Red Gate\SmartAssembly 5\OpenSesame123.settings
C:\Program Files\Red Gate\SmartAssembly 5\SmartAssembly.settings
But thats it, no tries to access the database, nada, nyet. / comments
Still trying to make it work, to no avail yet.
Some more details:
Tracing it with procmon, I see accesses toC:\Program Files\Red Gate\SmartAssembly 5\FSharp\Windows
C:\Program Files\Red Gate\SmartA...
I just updated to the latest EAP build (121) and everything is back to normal. Whatever was wrong in build 114, its gone in 121. / comments
I just updated to the latest EAP build (121) and everything is back to normal. Whatever was wrong in build 114, its gone in 121.
Hum, had the same problem again, with the version that worked last time and again, after updating to the latest 5.5 release its now working. Would be really great to figure out what could cause this. / comments
Hum, had the same problem again, with the version that worked last time and again, after updating to the latest 5.5 release its now working. Would be really great to figure out what could cause this.
Now that is weird, running SA in the build task I get this error, standalone it works. / comments
Now that is weird, running SA in the build task I get this error, standalone it works.
Sorry, forgot to mention it: its 5.5.114 because it solves the problem I have with 5.1 (see F0038426)
To make things more interesting, I have a VM which is a clone of my dev machine which I use for testing sometimes, just installed 5.5 there, and it works fine in both build and standalone. / comments
Sorry, forgot to mention it: its 5.5.114 because it solves the problem I have with 5.1 (see F0038426)
To make things more interesting, I have a VM which is a clone of my dev machine which I use for...
Sorry for the late reply, didn't get the notification it seems.
No, the mentioned assembly is merged, but not bound using reflection. / comments
Sorry for the late reply, didn't get the notification it seems.
No, the mentioned assembly is merged, but not bound using reflection.