I am using the method to create a SQL Server Data Tool / Data-level Application Framework / Visual Studio Database Project . The same project, when manually created by Visual Studio in a single configuration, creates approximately 10 seconds without exception and in a relatively short time. However, when programmatic is created through BuildManager.Build, then I have to face a complete death of first chance exceptions, all of which are in the antarctic namespace. This makes the build process very slow. Is this happening because the BuildManager.Build program is running in debug mode? Does anyone know how to get rid of the first opportunity expedition and hope that the process of build will accelerate?
The first chance exception is thrown in both cases, when you are doing this, for some reason For, you are attached as a debugger in the child's process, which freeze the process for each exception, which governs your process, which probably ignores it and restarts the app - when the first chance is not enough All of them are running as a debugger.
Exceptions are thrown because STDT (as you might have guessed) to parse SSDT T-SQL and it did not find anything that it does not like.
The key to this is finding out why you are attached as a debugger, it is normal with BuildManager. Builder? The MSDN article is not particularly helpful if you can find a way to run the build without applying it as a debugger, then it will take it back to normal speed.
FYI - Release / debug build should not make any difference in this matter.
No comments:
Post a Comment