Comments
Sort by recent activity
Use of build variables and parameters comes to mind :twisted: , evaluation of macros, etc. all inside the .saproj file, which in the end means no more project file but a .target file instead. Would make it really a lot easier to setup SA projects with outputs from other results of the build process, depending on build type.
And also that little problem of multiple invocations of the SA build task which reuses the database connection instead of having one for each instance would be nice to see improved (yes, i still have this problem occasionally and its always related to other extensions)
I would also like to be able to configure SA without having an assembly ready. Often I know what I want but I need it to happen in the build pipeline, and not always I have the intermediate executable available. In those cases I have to create the project by hand and cant use the GUI. / comments
Use of build variables and parameters comes to mind :twisted: , evaluation of macros, etc. all inside the .saproj file, which in the end means no more project file but a .target file instead. Would...
Are there going to be any changes to the build system in v6?
Improvements to how the MSBuild task accesses the database?
Better support for build configuration? / comments
Are there going to be any changes to the build system in v6?
Improvements to how the MSBuild task accesses the database?
Better support for build configuration?
On a side note, unrelated to the problem - while it is tempting to embedd or merge log4net into your assembly, by its license you are not allowed to do so. This is a general problem of using OSS assemblies in your protected products. We are required to deliver those assemblies, modified or original, as standalone assemblies by most of the licenses for OSS. / comments
On a side note, unrelated to the problem - while it is tempting to embedd or merge log4net into your assembly, by its license you are not allowed to do so. This is a general problem of using OSS as...
I am a bit short on time but will try to setup a sample project and send it over. Might take some days though. / comments
I am a bit short on time but will try to setup a sample project and send it over. Might take some days though.
Direct stack decoding with ASCII renaming, report comes from a log file. / comments
Direct stack decoding with ASCII renaming, report comes from a log file.
Definitely no 3rd party assemblies involved.
Here is the (for me) undecodeable stack trace:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at #0o.#1o.#2o(Int32 )
at (Int32 )
at Uniwares.Net.Dns.Message.DomainUtils.DecodeDomain(Byte[] data, UInt16 start, UInt16& length)
DecodeDomain is wrapped in a try/catch(IndexOutOfRangeException) yet... you see. The #0o.#1o.#2o(Int32 ) is no longer inside our code. / comments
Definitely no 3rd party assemblies involved.
Here is the (for me) undecodeable stack trace:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at #0o.#1o.#2o(Int32 &...
"Ingeniously simple" answer... :lol:
Not what I wanted to hear but it was expected.
*goes off to find two thousand *nix developers in need of SA*NIX* / comments
"Ingeniously simple" answer... :lol:
Not what I wanted to hear but it was expected.
*goes off to find two thousand *nix developers in need of SA*NIX*
Yes, it actually seems to start processing the input file, had an error in another one and it reported a missing reference before any database error.
Right now I am at the point of giving up on using the MSBuild task and rewriting all my builds. Cleaned the build machine from all remains of redgate and smartassembly - assemblies and registry entries - reinstalled SA 5.5 from scratch and get the same error. I deleted the database, reset file and folder security, cleaned the GAC, but all of that with no better results.
I even reinstalled SA 5.0 just to see the same result. Which now points to something pretty off the reach of SA, probably something in the build pipeline, interfering with SA and its access to the database. What that could be, I have not the slightest idea.
Keep you posted. / comments
Yes, it actually seems to start processing the input file, had an error in another one and it reported a missing reference before any database error.
Right now I am at the point of giving up on usi...
You wont believe it but the culprit is a VS2010 extension which has nothing to do with the build process. VSCommands2010 http://vscommands.com
Among some really useful things, it "enhances" the output window with color coding. Seems that during that process it messes with the build tasks in general.
Uninstalled, SA works fine. Reinstalled, SA breaks. / comments
You wont believe it but the culprit is a VS2010 extension which has nothing to do with the build process.VSCommands2010 http://vscommands.com
Among some really useful things, it "enhances" the outp...
After digging deeper into it, the main problem seems to be that in the failure case, the build system used is mixed up.
See: Output file "obj\Release\MyProject.pdb" does not exist.
Using "Csc" task from assembly "Microsoft.Build.Tasks.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Task "Csc" (TaskId:16)
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Csc.exe .... (TaskId:16)
Done executing task "Csc". (TaskId:16)
against: Output file "obj\Release\MyProject.pdb" does not exist.
Task "Csc" (TaskId:16)
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Csc.exe .... (TaskId:16)
Done executing task "Csc". (TaskId:16)
Other differences are:
* some build symbols defined differently (might be a result of the build system versions)
* startup folders different (VS2010 IDE installation against solution base)
I guess that this kind of problem might occur in other situations with other extensions I guess, so it might be interesting to investigate this deeper. / comments
After digging deeper into it, the main problem seems to be that in the failure case, the build system used is mixed up.
See:Output file "obj\Release\MyProject.pdb" does not exist.
Using "Csc" task ...