[Closed] Visual Studio 2013 directory for SDK plugin wizard stuff

If you are on windows x64 then it’s here:

C:\Program Files (x86)\Microsoft Visual Studio XXX \VC\vcprojects\

XXX is the visual studio version number.

Thanks.

Now I see the plugin wizard option in VS’s new project dialogue, but selecting it fails and I get a message”Creating project ‘maxProject1’…project creation failed “

update: seems that there is a lot of hoops to jump to get this working

The plugin files must be write enabled

The 2013 plugin wizard requires Visual C++ 2010 Service Pack12 to be installed, even if you are using VS2013.

If I knew more about VS, I would just create my own template for a Max plugin project.

You are 100% sure you have the path set correct in the vsz file?

On mine its:

Param= "ABSOLUTE_PATH = c:\Program Files\Autodesk\3ds Max 2015 SDK\maxsdk\howto\3dsmaxPluginwizard"

for 3dsmax 2015 SDK.

Also make sure your project is created in a folder you have full access to…
I also usually run Visualstudio by right-clicking and ‘running as administrator’ (Don’t know if that helps you, but give it a shot).

I have been trying to get VS 2013 set up for diving into some SDK plugins. I’ve tried off and on for a few years to tip my toe into it to no avail.

When I copy the thee files to VC/VCProjects, no preset appears in the new project settings.

When I drag the VSV file into the VS 2013 UI, I get this message:

Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the “Migration Report” displayed after clicking OK.

• 3dsmaxPluginWizard, “C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCProjects\3dsmaxPluginWizard.vsz”

No changes required
These projects can be opened in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.

• 3dsmaxPluginWizard, “C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCProjects\3dsmaxPluginWizard.sln”

I have checked, double checked, triple checked the directories/paths and file permissions. What is the magic for getting a project started in VS 2013? :banghead:

Are you sure you are coping them into the correct folder and have edited the file with the correct path as the readme says?

3dsmaxPluginWizard.ico
  3dsmaxPluginWizard.vsdir
  3dsmaxPluginWizard.vsz

that last file has this in it:

  VSWIZARD 7.0
  Wizard=VsWizard.VsWizardEngine.11.0
  
  Param="WIZARD_NAME = 3dsmaxPluginWizard"
  Param="ABSOLUTE_PATH = C:\Program Files\Autodesk\3ds Max 2015 SDK\maxsdk\howto\3dsmaxPluginWizard"
  Param="FALLBACK_LCID = 1033"

Those files are copied to here:

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

When you generate a project it will be located under “File->New project->Visual c++”

I run with VS 2013 without problems, but I also had to do this:

The SDK template overrides the vs version number.
The file is located here:

\maxsdk\ProjectSettings\propertySheets\3dsmax.general.project.settings.props

Edit this line:

 <PlatformToolset>v110</PlatformToolset>

Just comment it out like this:

<!–<PlatformToolset>v110</PlatformToolset>–>

That way the project will use the correct compiler.
(VS 2013).

If not the projects would default to the wrong compiler, and would not be ‘upgraded’ to VS 2013 compiler.

Please carefully read Kevin Vandecar’s blog here:

3ds Max C++ SDK Training and fixed 3ds Max 2013 Plugin Wizard

Follow his instructions for installing the plugin wizard… I had no problems compiling an empty plugin project after following his guidance.

Also, you should adhere to the versions of Visual Studio that were used to create the specific version of 3ds Max SDK (there are exceptions to the rule). You can find out which version of Visual Studio is recommend for each 3ds Max version in the SDK Requirements section here (look in the “About the 3ds Max SDK” tab):

SDK Requirements

Thanks for the input Stig. Unfortunately, I still haven’t gotten it.

Michael, thanks. I have read that document very carefully. And I downloaded that updated wizard file. However, I’m not sure that is the issue. That file was posted in 2013. The Max 2015 SDK comes with an updated wizard that includes information for VS 2012 (whereas that older file only has information for installing in VS 2010). So I’m assuming that the wizard files for Max 2015 are more valid than the ones on the GetCoreInterface site. That being said, I tried it as well.

1. Install VS 2013
2. Install Max 2015 SDK
3. Open the .VSV file and make sure the path points to …/maxsdk/howto/3dsmaxplugins and that the version is set to 11.0
4. Copy the .ico, .VSV and .VSDIR files from the maxsdk/howto/3dsmaxplugins folder to the VS Install/VC/Express/VCProjects folder and make writable. For good measure, copy same files to /VC/VCProjects and make them writable.

Over and over. No such luck.

But guess what?

When I opened the maxsdk/howto/howto.sln … all of a sudden the Plugin Wizard has appeared inside VS.

WTF?

So I closed VS and re-opened via my VS 2013 icon and the wizard was gone.

So then after considering a trip to the bar, I dove back in and round and round.

Long story short, there are now two versions of VS 2013 on my system: an express edition and the VS Community Edition (the newer full version of VS that is equivalent in function to the VS Pro). The express edition was the version opening when I press the icon, and the newer, full community edition opens when I double-click the solution. This was not clear to me since I only ever installed the community edition of 2013 (as far as I knew and understood). In fact, I had copied all the files to both locations where the instructions say (for Express and full) just for good measure–but the 2013 Express was never working.

I’m am sharing this to 1) Expose my own ability to become confused and 2) Help anyone else who runs into the same confusion.

Far from “done” because this was just getting started… but at least now I can hopefully move on to actual pragmatic discussions.

Next tidbit I learned was not good after I learned something else – so I edited and removed the info. Now to go away and only come back when I’ve got something substantial to share or if others share info.

In the end I’m moving to the older version of VS as recommended in SDK and hints above… despite the hints that others are using VS 2013. I can only get C# to compile on 2013 and not Max’s C++ SDK. Of course I’m interested in seeing more on this discussion.