ASP.NET 5 RC Export Template Not Working

[TLHamilton]

When I use the File > Export Template function on an ASP.NET 5 project everything seems to go fine until I create a new project with the template. The Solution Explorer for the new project just does not show any of the project files.

[sayedihashimi]

@TLHamilton thanks for the report. I'm not sure what the status of File->Export Template is. I think it may not work for several project types.

I've opened an internal TFS bug so that we can reach out to the team that owns that.

TFS:167861

[jjcollinge]

This still appears to be an issue, any news on when this is likely to resolved? or does anybody know a work around?

[senj]

Is there a workaround? The asp.net 5 templates provided in VS must have been created somehow?

[jmurphzyo]

I found the work around rename the template file inside the zip to the correct name. It took me two hours to figure this out.

[sayedihashimi]

We have not yet looked at this. The team is heads down converting from dnx to dotnet.

[senj]

can you give an example please? What is the "correct name"? solutionname?

I found the work around rename the template file inside the zip to the
correct name. It took me two hours to figure this out.

—
Reply to this email directly or view it on GitHub
#306 (comment).

[jmurphzyo]

@senj

• Step 1. Create a asp.net 5 template and use the VS export template tool to auto generate a template zip file.
  
• Step 2. Extract the contents from the generated zip file and open the file “MyTemplate.vstemplate”.
  
• Step 3. Locate the“<Name></Name>”column and copy the information inside.
  
• Step 4. Rename the “MyTemplate.vstemplate” to “CopiedInformation.vstemplate”
  
• Step 5. Now zip the newly edited content.
  
• Step 6. Replace the zip file that was automatically generated by the visual studio tool.
  
• Step 7. Enjoy your newly created asp.net 5 template!!!

[senj]

Thank you very much for this grad instructions. Will try it soon. Greetings
Am 11.03.2016 7:59 nachm. schrieb "Justin Murphy" <[email protected]

:

@senj https://github.com/senj

Step 1. Create a asp.net 5 template and use the VS export template
tool to auto generate a template zip file.
[image: step1]
https://cloud.githubusercontent.com/assets/7680404/13712359/d1abebda-e788-11e5-981d-132fc19213af.jpg

Step 2. Extract the contents from the generated zip file and open the
file “MyTemplate.vstemplate”.
[image: step2]
https://cloud.githubusercontent.com/assets/7680404/13712363/daba458c-e788-11e5-96cb-9ec360819e38.jpg

Step 3. Locate the“”column and copy the information
inside.
[image: step3]
https://cloud.githubusercontent.com/assets/7680404/13712354/c93bcbf0-e788-11e5-9b6d-2f4bed5bcfb5.jpg

Step 4. Rename the “MyTemplate.vstemplate” to
“CopiedInformation.vstemplate”
[image: step4]
https://cloud.githubusercontent.com/assets/7680404/13712370/e0e28ece-e788-11e5-96a9-a22119d80383.jpg

Step 5. Now zip the newly edited content.
[image: step5]
https://cloud.githubusercontent.com/assets/7680404/13712379/e946e754-e788-11e5-93d2-454142593029.jpg

Step 6. Replace the zip file that was automatically generated by the
visual studio tool.
[image: step6]
https://cloud.githubusercontent.com/assets/7680404/13712386/edc3ae20-e788-11e5-88d4-5aeaa150e428.jpg

Step 7. Enjoy your newly created asp.net 5 template!!!

—
Reply to this email directly or view it on GitHub
#306 (comment).

[webtools-bot]

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!