Comments
Sort by recent activity
All 32bit, no GAC dependencies. Will do a check with windbg and let you know. / comments
All 32bit, no GAC dependencies. Will do a check with windbg and let you know.
Ok Alex, this was the missing piece of information. The files are exactly where you said.
This should be part of the error message, could even place a link in it to open the folder where they are saved.
Thanks. Solved. / comments
Ok Alex, this was the missing piece of information. The files are exactly where you said.
This should be part of the error message, could even place a link in it to open the folder where they are s...
Should they be in the database? As I understood the message (don't remember the precise wording now) SA didn't save the report because the database didn't contain information about this specific application.
If they are, how do I transfer them to the machine where the app was built? / comments
Should they be in the database? As I understood the message (don't remember the precise wording now) SA didn't save the report because the database didn't contain information about this specific ap...
Nick: will try and see what's happening with that. Jason: since I am using it as a aftercompile step, i cant change the output to something else or other build steps after will fail. But anyway, it doesn't make any sense, why would it fail to read but succeed to write? / comments
Nick: will try and see what's happening with that.Jason: since I am using it as a aftercompile step, i cant change the output to something else or other build steps after will fail. But anyway, it ...
Oh, one more thing. CreatePDB=0 works fine when I change the build settings from "full" or "pdb-only" to "none". While I might understand that if SA depends on the PDB creation settings of the compiler it could report an error, it definitely should not be the current one. / comments
Oh, one more thing. CreatePDB=0 works fine when I change the build settings from "full" or "pdb-only" to "none". While I might understand that if SA depends on the PDB creation settings of the comp...
Just ran it under procmon and saved the log for both cases, with and without pdb creation.
For me it looks like SA shoots in its own foot since VS is closing the file before passing control to SA.
The difference is that with CreatePDB=0 SA tries to delete the pdb file which VS created while it is still open for reading. With CreatePDB=1, SA writes to a new .pdb file in the temp folder then calls {CLRTools}.exe to process both files and does NOT try to delete the file.
Can send you the logs. / comments
Just ran it under procmon and saved the log for both cases, with and without pdb creation.
For me it looks like SA shoots in its own foot since VS is closing the file before passing control to SA.
...
No, there is no try/catch at all. And as I could see, in pretty much every ctor SA seems to insert this preventive catch all, even in emtpy and default ctors. but only the ctors with code in it actually have the outer catch.
Seems pretty weird to me. / comments
No, there is no try/catch at all. And as I could see, in pretty much every ctor SA seems to insert this preventive catch all, even in emtpy and default ctors. but only the ctors with code in it act...
My sincere apologies, 5.1 build 3 is NOT broken. I have no idea still what broke, but after rebooting the build machine and reinstalling 5.1 everything went back to normal and the output files are protected as they should be. / comments
My sincere apologies, 5.1 build 3 is NOT broken. I have no idea still what broke, but after rebooting the build machine and reinstalling 5.1 everything went back to normal and the output files are ...
True, i wont need a foreground thread. Still its a nasty trap to fall into, even if its not SA's fault. One of those cases where its hard to draw the line. But might be worth at least a warning in the user manual (or even at the settings page). / comments
True, i wont need a foreground thread. Still its a nasty trap to fall into, even if its not SA's fault. One of those cases where its hard to draw the line. But might be worth at least a warning in ...
No, not using this option. / comments
No, not using this option.