The first time you try after a reboot, Visual Studio doesn't connect with Inventor?
After it makes a connection, are you able to close VS and Inventor, then restart them and reliably get a connection?
Run VS -> Open Project -> Run Inventor -> Create empty Intent assembly through "Create new file" -> There is a connection between Intent and VS -> Close assembly -> Open my app -> Generate 3D -> There is a connection -> Close Inventor -> Close VS -> Run VS -> Open Project -> Run Inventor -> Run my app -> Generate 3D -> No connection.
I need to repeat trick with empty Intent Assembly for creating connection between Intent and VS every time when I close VS.
After you get a connection and Generate 3D: can you close that model, Generate 3D again and get a connection? Or do you have to Create New File again?
Yes, I have a connection if I close 3D and generete again through my app. It works so long as VS is open.
I am not able to get a connection to VS using the approach above. I am able to run the solution from VS to launch a new instance of Inventor, but the debugging cycle time of that approach is too long (waiting on Inventor to start).
Are there some settings in VS that I need?
I had trouble throughout the weekend trying to use ETO Studio R2. I have done the following already:
i7-2820QM @ 2.3GHz Quad Core
16GB RAM, 256GB SSD, Quadro 2000M
Windows 7 x64, SP1
Inventor 2013 - Build 138
ETO 6.1 - Build 140
I want to make sure you know that you can't debug Intent code even if you do get a connection this way. The only way to debug Intent code is to start Inventor from Visual Studio.
Do you have any Visual Studio add-ins or extensions loaded? Can you post the About dialog from your install of Visual Studio?
I learned that from the team here this morning. That is a bummer. I will be logging ADN issues with our discoveries on projects that depend on reference project libraries relative to performance when we run Inventor from VS for debugging.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!