3DX - VSTA editor fails to launch

[solid7]

I'm so frustrated. I've tried 3 times to install VSTA, and while I can get the dialog box in the macros function that allows me to create or import VSTA libraries, I cannot edit. Every time I try, I get a message that says, "the editor has failed to launch. Try to reinstall VSTA 2013 using DSSVSTA2013Installer".

Here's where I'm at:

I have the correct version of both VSTA and Visual Studio installed, per documentation. (2017x requires VSTA 2013 and VS 2013 Professional)
I have the .NET 3.5.1
I am unable to install .NET 4.5.2, as required, since Windows 10 already has a later version installed as a system requirement.

I also get a dialog that talks about a command line build for Visual Studio, but I'm not really sure what to do with the info.

Anyone know how to get this resolved?

 

[Little Cthulhu]

Hi.

Start VS developer's command prompt and run clrver
It should display the list of all installed versiona of .net framework. Post it here.

 

[Little Cthulhu]

To be honest, I believe odds are high 2017x is not supported on Windows 10. If so better not consider this release as a long-term solution or downgrade Windows to version 8.1

 

[solid7]

C:\Program Files (x86)\Microsoft Visual Studio 12.0>clrver

Microsoft (R) .NET CLR Version Tool Version 4.0.30319.33440
Copyright (c) Microsoft Corporation. All rights reserved.

Versions installed on the machine:
v2.0.50727
v4.0.30319

C:\Program Files (x86)\Microsoft Visual Studio 12.0>

 

[Little Cthulhu]

Great.

Install .net 4.6.2 then.
(and you can run clrver from VS 2017 console too)

 

[solid7]

It tells me that a later update is already installed.

 

[ferdo]

Hi

Personally I'm using VS2013 Express in 3DEx 20202x cloud but not with VSTA (by the way, on my laptop I'm getting an error when trying to create VSTA library, I have to check in few days on another pc...).
I'm using known references by 3DEx copied on the local folder so I'm using dll files coming from each release (like Little Cthulhu already specified in another post for V5).

Regards
Fernando

https://www.youtube.com/playlist?list=PL9mSHa4SOedV3dr0D3kfIWFUg7mIYm94k

 

[solid7]

I can create libraries, I just can't edit them, as 3DX is unable to open the editor.

 

[Little Cthulhu]

run clrver from VS 2017

And what did it say?

I can create libraries, I just can't edit them, as 3DX is unable to open the editor.

What ferdo meant is that he doesn't use VSTA at all, only Visual Studio. Would you consider this as a solution?

 

[solid7]

It doesn't say anything, because I actually uninstalled it, to try to get to the bottom of this.

Of course I'd consider that as a solution, so long as Visual Studio works as an editor and debugger from 3DX. I just thought that we'd have to run the installer for connectivity. But I have visual studio 2013 Pro ready to go...

 

[Little Cthulhu]

Please refer to this article to find out which .net framework version you have installed.

 

[solid7]

I already posted earlier which versions I have installed. All I was telling you, is that I uninstalled VS 2019, so as not to muddle the process.

 

[solid7]

So I'm still not installed. What did I miss?

 

[Little Cthulhu]

What you posted was output from clrver tool, whilst there're also registry keys described in the article I've provided.

Anyway, try running .NET Repair Tool
What Windows 10 version (i.e. 1703) do you use?

 

[solid7]

I'm running Windows Enterprise 10 (1809 - Build 17763.914)

 

[solid7]

And today, for no particular reason, VSTA launches.

OK, Catia. Whatever.

 

[itsmyjob]

not sure if macro libraries have creation/edition capabilities based on your role (Owner or Leader of your Collab Space)

I would try if I had VSTA installed but I don't

Eric N.
indocti discant et ament meminisse periti ​

 

[solid7]

Nope. Have tools, will create. I only have Leader role for this particular collaborative space, but once the tools decided to work, I was able, no problem.

I actually suspect that LC was right, and that something isn't supported in Windows 10. I elevated the question to our Dassault Rep.