SDK VSIX Project won't compile without a resource file - by rpierry

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 515485 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 11/29/2009 12:33:31 PM
Access Restriction Public


When starting with a blank VSIX Project, after adding a VSCT manually, the project won't compile, giving the following error in the SDK build targets file:

No resource file set the resource merger

You can work around this by first adding a resource file and then manually editing the csproj file to include <MergeWithCTO>true</MergeWithCTO> under the resource file.  Even if this bug is marked "By Design" there needs to be an easier way to know you have to set this element.
Sign in to post a comment.
Posted by Microsoft on 12/17/2009 at 9:05 AM
Yes, the intent is to merge them. The VS Package wizard will be available in the C# and VB Extensibility nodes for RTM.
Posted by rpierry on 12/3/2009 at 12:38 PM
Ah. Apparently the SDK creates 2 sections in the new project dialog
Visual C# / Extensibility which has all the VSIX and MEF extensibility stuff
Other Projects / Extensibility which has the wizard and the old style stuff.

This is confusing. Is the intent to merge these into one or keep them around in 2 separate locations like this?
Posted by rpierry on 12/3/2009 at 11:45 AM
Where is this wizard available?

It doesn't show up under the regular VSIX project templates with the rest.
Posted by Microsoft on 12/3/2009 at 11:18 AM
Thank you for reporting this. For creating packages with VSCT files, the recommended approach is to use the Visual Studio Integration Package wizard, and not manually adding a VSCT file.

We will evaluate this as something to change for a future VS Release but for the VS 2010 SDK, our recommendation is to start with package wizard project template.
Posted by Microsoft on 12/3/2009 at 3:32 AM
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.

Thank you
Posted by rpierry on 12/2/2009 at 6:40 AM
Easiest way to reproduce -
1. start with the WPF Tool Windows sample from the vsx msdn code gallery
2. delete the Resources.resx file from the solution
3. try to compile

You can also reproduce it by starting with a blank project created using the VSIX Project template, adding a VSCT file, opening the csproj and setting generate package def and all the other related elements to "true" and then trying to compile, but starting with the tool window sample is easier.
Posted by Microsoft on 12/2/2009 at 1:23 AM
Thanks for reporting this issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please give us a demo project to demonstrate this issue so that we can conduct further research?

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.

Visual Studio Product Team
Posted by Microsoft on 11/30/2009 at 2:21 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(