|
#1
|
|||
|
|||
My testing suggests you need to target .NET 2.0 (will have to investigate further to see if it's possible to support 4.0).
If you use Any CPU for the platform, the compiled .NET action can be registered and used in 32- or 64-bit Visual Build, but I suspect that actions with a user interface will not work properly in the 64-bit edition. |
#2
|
|||
|
|||
Thanks, I will give it a try an let you know
|
#3
|
|||
|
|||
I am working on creating a new version, when attempting to run a BLD file that registers the DLL I get the following error from within VB8
4/4/2012 1:51:20 PM: Building project step 2 - Register DLL... RegAsm : error RA0000 : An error occurred while writing the registration information to the registry. Administrator permissions are needed to use the selected options. Use an administrator command prompt to complete these tasks. Process completed with exit code 100 4/4/2012 1:51:20 PM: Step '2 - Register DLL' failed 4/4/2012 1:51:20 PM: Build ended (elapsed = 00:00:00). |
#4
|
|||
|
|||
I fogot to add the acutal command line thats run, it appears to defualt to the highest framword version installed on the box. The assembly is trageting the 2.0 framwork
C:\Windows\Microsoft.NET\Framework\v4.0.30319\rega sm.exe C:\TFS\SCM\Dev\ACE.VisualBuild.Solution-DEV1\ACE.VisualBuild.SelectVersion\bin\Release\ACE .VisualBuild.SelectVersion.dll /nologo /s /codebase |
#5
|
|||
|
|||
regasm does require elevated privileges to register a COM assembly.
http://kinook.com/Forum/showthread.php?t=2258 The COM Register action use the highest installed framework version that is found for locating regasm.exe. You can override the regasm.exe on the Register tab. http://www.kinook.com/VisBuildPro/Ma...omregister.htm |
#6
|
|||
|
|||
Great, thanks for the quick turn around!
|
#7
|
|||
|
|||
I found as I created a new action and compared the scripts with my previos version there appears to be a new property that I cant find information on. If I open up a build file I see the following property added to my custom action.
<buildfailsteps type='11'>0</buildfailsteps> If I try to add exisitng actions to the same script the added actions also have this value added but the exisiting actions do not get modified when saving to have this new propery. Can you tell me more about this and what the values represent? |
|
|