• 0

[C#] Can't create VSIX file. Please help.


Question

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.

Link to comment
https://www.neowin.net/forum/topic/1129634-c-cant-create-vsix-file-please-help/
Share on other sites

2 answers to this question

Recommended Posts

  • 0

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

This topic is now closed to further replies.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!