3 posts in this topic

Posted

I can't seem to find any article that tells me how to fix my problem. I've tried cleaning and rebuilding everything with no go. I've put together some free controls for the public to use and I want to make a VSIX file. Seems simple enough, so I go download the Visual Studio 2012 SDK and install it, create the VSIX according to this blog: http://timheuer.com/blog/archive/2012/03/07/creating-custom-controls-for-metro-style-apps.aspx exactly how he has it but when I try to compile the vsix project it says:

The target "PkgdefProjectOutputGroup" does not exist in the project. I'm tugging my hair out here this should not be this hard. I can manually move the files to the extensions folder for vs and get it to show up in VS and work with my projects why can't I create a VSIX file of it? So far googling that error retrieves no results.

Share this post


Link to post
Share on other sites

Posted

Wow after several hours of digging I finally figured out what I needed to do. Remove the property in the reference in the VSIX project. What a head ache that was.

Share this post


Link to post
Share on other sites

Posted

I created a project template for my sample ASP.NET MVC4 project in visual studio 2012 and then export template from file menu. Next I created a Vsix project where I added exported template zip file and its references in VsixManifest. Then I build the project which succeeded. I went to the location where I find the .vsix file and double click on it to install that template. When I opened new instance of visual studio I was able to see that template in the visual studio new project dialogbox. It worked until this point. I need to give the .vsix file to different users in my team. As soon as they double click on file template should create on there project dialog box. It did. But getting problem at resolving references. I tried to enable nuget package manager. Still same issue on their machine. This technique resolved references on my machine but not there machine. Is there any way to fix the issue of resolving dll references. Help would be appreciated.

Thanks,
Munni

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.