msbuild - How to build tSQLt from source? -
can build same tsqlt.zip hosted on sourceforge building source? how do that?
i've checked out head (currently r200) of tsqlt svn repository using command:
svn checkout https://tsqlt.svn.sourceforge.net/svnroot/tsqlt tsqlt
there file called buildnotes.txt in build directory describes build process. first step looks this:
setting tsqlt build notes: 1. must run msbuild command line once before running build. reason first time prompts signing password. signing password is: p@$$30rd gets somehow stored internally in windows, , not need re-entered again. here example of msbuild command: c:\projects\tsqlt.sourceforge\tsqltclr\tsqltclr>c:/windows/microsoft.net/framework/v2.0.50727/msbuild.exe tsqltclr.csproj /p:configuration=release /nologo
when run example command see password prompt:
i paste in password "p@$$30rd" , click ok. password apparently not correct:
the command output of msbuild looks this:
c:\users\iain.corp\skydrive\software\sql server\tsqlt\svn\tsqlt\tsqltclr\tsqltclr>c:/windows/microsoft.net/framework/v2.0.50727/msbuild.exe tsqltclr.csproj /p:configuration=release /nologo build started 05/04/2013 19:07:15. __________________________________________________ project "c:\users\iain.corp\skydrive\software\sql server\tsqlt\svn\tsqlt\tsqltclr\tsqltclr\tsqltclr.csproj" (default targets): target getframeworkpaths: not locate .net framework sdk. task looking path .net framework sdk @ location specified in sdkinstallrootv2.0 value of registry key hkey_local_machine\software\microsoft\.netframework. may able solve problem doing 1 of following: 1.) install .net framework sdk. 2.) manually set above registry key correct location. target resolvekeysource: c:\windows\microsoft.net\framework\v2.0.50727\microsoft.common.targets(1728,7): error msb3321: importing key file "signingkey.pfx" canceled. done building target "resolvekeysource" in project "tsqltclr.csproj" -- failed. done building project "tsqltclr.csproj" -- failed. build failed. c:\windows\microsoft.net\framework\v2.0.50727\microsoft.common.targets(1728,7): error msb3321: importing key file "signingkey.pfx" canceled. 0 warning(s) 1 error(s) time elapsed 00:00:07.39 c:\users\iain.corp\skydrive\software\sql server\tsqlt\svn\tsqlt\tsqltclr\tsqltclr>c:/windows/microsoft.net/framework/v2.0.50727/msbuild.exe tsqltclr.csproj /p:configuration=release /nologo build started 05/04/2013 19:07:15. __________________________________________________ project "c:\users\iain.corp\skydrive\software\sql server\tsqlt\svn\tsqlt\tsqltclr\tsqltclr\tsqltclr.csproj" (default targets): target getframeworkpaths: not locate .net framework sdk. task looking path .net framework sdk @ location specified in sdkinstallrootv2.0 value of registry key hkey_local_machine\software\microsoft\.netframework. may able solve problem doing 1 of following: 1.) install .net framework sdk. 2.) manually set above registry key correct location. target resolvekeysource: c:\windows\microsoft.net\framework\v2.0.50727\microsoft.common.targets(1728,7): error msb3321: importing key file "signingkey.pfx" canceled. done building target "resolvekeysource" in project "tsqltclr.csproj" -- failed. done building project "tsqltclr.csproj" -- failed. build failed. c:\windows\microsoft.net\framework\v2.0.50727\microsoft.common.targets(1728,7): error msb3321: importing key file "signingkey.pfx" canceled. 0 warning(s) 1 error(s) time elapsed 00:00:07.39
the output contains message "could not locate .net framework sdk". have install make work?
it looks there specified wrong password. can open tsqltclr\tsqltclr.sln
in visual studio interface , try type or change password. in both cases got "the old password invalid" message.
actually not need strong name key file. strong name prerequisite sql clr assembly , can use file, including own. can create new key file same name , password , build assembly.
if have visual studio installed not need .net framework sdk because can sign assembly through interface. if have not vs must install sdk able use sn.exe part of sdk.
i have tried this solution, did not succeed too
Comments
Post a Comment