VDS Configuration Editor Use and Training

VDS Configuration Editor Use and Training

apodsim
Contributor Contributor
983 Views
11 Replies
Message 1 of 12

VDS Configuration Editor Use and Training

apodsim
Contributor
Contributor

Program Environment:

  • Vault Professional and Data Standard 2021 26.0.63.0
  • Microsoft Visual Studio Enterprise version 15.9.33
  • PowerShell Extension for Visual Studio 2017
  • GitHub Extension for VIsual Studio

apodsim_0-1615398889066.png

 

I would like to use the VDS Configuration Editor referenced in Knowledge Base and having difficult in getting past Visual Studio setup as shown in ...ConfigurationEditor.pptx .  All of the bullet points under Get Started have been added including subscription to the GitHub Repository where all of the tutorial and sample files are located.

 

The VDS-Configuration-Editor-2020_2021_Master.zip is shown below.  

apodsim_1-1615398999005.png

..ConfigurationEditor.pptx Slide 11 shows API-2020-Onbording_PowerShell.zip which is not part of the above.

 

After configuring the VDS Editor Templates the Powershell and XAML Snippets on Slide 10 were added as shown below.

apodsim_2-1615399413618.png

..ConfigurationEditor.pptx Slide 11 shows how the folders should be structured.  This shows the missing API-2020-Onbording_PowerShell.zip.

Screenshot 2021-03-10 091542.png

 From ..ConfigurationEditor.pptx Slide 12 , the CUP is set to x64

apodsim_3-1615400554105.png

 

..ConfigurationEditor.pptx Slide 13 shows Vault/addinVault/Menus lists the file Default.pc1.  There are no files or folders included from the VDS-Configuration-Editor-2020_2021_Master.zip

 

..ConfigurationEditor.pptx Slide 14 shows files under the VDS-Configuration-Editor folder. The only folder is Properties as shown below

apodsim_4-1615402756506.png

 

Any advise on where the missing files shown are located will be appreciated.

Accepted solutions (1)
984 Views
11 Replies
Replies (11)
Message 2 of 12

Markus.Koechl
Autodesk
Autodesk

The editor environment might have grown too complex over the years. I already started to clean it up; so, expect a 2021 editor download supplemented by a video on how to download and activate it. But note - the editor does not include any Data Standard Configuration file; the editor provides links to the VDS ProgramData folders only. Anyway - you will see in the video.

Thanks for bringing the complexity of the tool to my attention.



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes
Message 3 of 12

apodsim
Contributor
Contributor

Thanks for the update. I am looking forward to see the changes noted.

0 Likes
Message 4 of 12

Markus.Koechl
Autodesk
Autodesk
Accepted solution

@apodsim: The Visual Studio solution updated for 2021 and removed all legacy files. The Powerpoint documentation added step-by-step instructions on downloading from Github, extract and open in Visual Studio. Be aware that the VDS Editor projects share the VDS configuration files; the configuration files are linked to the project instead. The embedded videos are recorded editing legacy (2019) configurations, but the principle applies to all newer VDS versions. I hope this helps you to get started.



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
Message 5 of 12

apodsim
Contributor
Contributor

When starting the VDS-Configuration Editor in VS 2017 a message message below appears.  When I download .NET Framework Version 4.7.2 and install, the message indicating that version is already installed.  How do I make VS use the installed Version 4.7.2?

apodsim_0-1615912282333.png

apodsim_1-1615912429529.png

 

 

0 Likes
Message 6 of 12

Markus.Koechl
Autodesk
Autodesk
It should accept the shown option: change the target to 4.6.1. By selecting this option you can open the solution. Then open the project properties and change back to 4.7 or 4.7.2.


Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes
Message 7 of 12

apodsim
Contributor
Contributor

VS 2017 help shows that .NET Framework can be changed by selecting the Solution Properties.and selecting the Applications tab.  The VDS-ConfigurationEditor Property Page does not show a WpfApplications tab as shown in the screenshot below that would allow for changing the .NET Framework version.

apodsim_0-1616007081745.png

 

0 Likes
Message 8 of 12

Markus.Koechl
Autodesk
Autodesk
Sorry, I haven't been precise enough: open the project's properties to change the version. Your .NET message lists it anyway saying, "The C# project "VDS-2021-Quickstart-Standard"...."


Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes
Message 9 of 12

apodsim
Contributor
Contributor

Under the Project tab "Properties" there is a tab, "Executable Properties" where you can select .Net Version to "net472".  Is this correct?

0 Likes
Message 10 of 12

Markus.Koechl
Autodesk
Autodesk

Open the Solution Explorer, navigate to each of the listed projects, and right-click to select Properties. On each project, select the .NET version as shown here: 2021-03-18_00-34-53.png



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes
Message 11 of 12

apodsim
Contributor
Contributor

This is the location I have been at before and not been able to progress further.  .NET Framework above 4.6.2 are not listed shown in Figure 1 and when I try Install other frameworks... the .NET Framework web page is launched.  When I download the .NET Framework  version 4.7.2 shown in Figure 2 and launch install, the message shown in Figure 3 indicates ,.NET Framework 4.7.2 is already installed, yet it is not listed under Target framework combo box.

 

Is related to using Visual Studio 2017?  Should I install VS 2019? 

Figure 1

apodsim_0-1616073344644.png

Figure 2

apodsim_1-1616073768420.png

Figure 3

apodsim_2-1616074217949.png

 

0 Likes
Message 12 of 12

Markus.Koechl
Autodesk
Autodesk

I hope you understand that I can't provide 1:1 support on setting up a Visual Studio environment. The Microsoft knowledgebase lists several reason/solution entries on this, like installing the latest updates on VS 2017 and/or checking the target architecture/environment PATH variable.

Upgrading to VS2019 might resolve the issue quicker as it uses 4.7.x as a base AFAIK.



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes