Search

Cannot open Webform.vstemplate by tushru2004

Active

1
0
Sign in
to vote
Type: Bug
ID: 779537
Opened: 2/19/2013 1:15:37 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I couldn't open a new webform by doing
1) Right click on the project -> Add -> Webform

I tried devenv /installvstemplates and denenv /setup

also uninstall and reinstall vs professional 2012

But when i do Right click on the project -> Add - > New Item-> Webform ...it works without a problem

PS: I also have Vs 2012 update 1 installed
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

1) Right click on the project -> Add -> Webform

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

Error : Could not find a part of the path 'C:\Program Files(x86)\Microsoft Visual Studio 11.0\Common7\IDE\ItemTemplatesCache\CSharp\Web\2033\Webform.zip\Webform.vstemplate'

Expected results

open a new webform
File Attachments
0 attachments
Sign in to post a comment.
Posted by tushru2004 on 4/17/2013 at 2:07 PM
The workaround doesn't seem to fix the problem for me. But i will try the next version
Posted by Microsoft on 4/15/2013 at 4:53 PM
Hi. We have this issue fixed for the next version of Visual Studio. If you ever run into it again, a workaround is to delete the following two cache files:

ProjectTemplateMRU.xml
SpecificFolderCache.xml

from the C:\Users\<yourUserName>\AppData\Local\Microsoft\VisualStudio\11.0\1033 folder.

Bill Hiebert
Web Tools Team
Posted by Microsoft on 2/19/2013 at 10:45 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 2/19/2013 at 1:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.