|
|
|
|
#1
08-28-2015, 08:35 AM
|
|||
|
|||
|
I will give it a try. I have a custom action that I wrote in VS2010 FW 4.0, that I use in my scripts. If I update to Version 9, I want to update the custom action to VS2013, can I use FW 4.5.2 for my custom action with VB 9x?
|
|
#3
08-28-2015, 11:19 AM
|
|||
|
|||
|
So far so good the power shell is working now I will test the upgrade of my custom action later.
I did notice that from 2012 r2 to 2012 r2 I didnt change the setting none but still in v9 it worked.
|
|
#5
08-31-2015, 08:07 AM
|
|||
|
|||
|
I have upgraded to v9x and the Power Shell scripts are now working thanks.
I am seeing something unfamiliar with the new version. When I open a script without setting any breakpoints and close VB I see a .user file created. Whats that about?
|
|
#6
08-31-2015, 08:25 AM
|
|||
|
|||
|
In v9 by default, Visual Build remembers the previously selected steps when reopening a project (stored in the .user file). To prevent this, uncheck Tools | User Options | General | Remember selected steps when reopening projects. The .bld.user file will still be created if you set breakpoints in a project (same as with v8).
|
|
#7
08-31-2015, 08:51 AM
|
|||
|
|||
|
Great thanks!
Getting back to the issue with Power shell, there is a field to override the path to the PS EXE is that necessary or should I leave that blank? In the help file it mentions a folder called Sysnative not sure what that means its not marked a a variable but I assume you mean System32
|
|
#8
08-31-2015, 01:33 PM
|
|||
|
|||
|
Is there a way to globally set that user setting for remembering last selected items. We have a lot of Build Team members and I don't want that file creating for global shared scripts.
|
 |
|
|
Hybrid Mode
