WSSF 2010 Open Source for Visual Studio 2012 - Requirements

Topics: General Discussion Forum, Service Factory Modeling Edition Forum
Feb 5, 2014 at 8:55 PM
Edited Feb 5, 2014 at 9:48 PM
I have built and installed the VSIX file for Visual Studio 2012.
Visual Studio 2012 does NOT have Guidance Package Manager.
In Visual Studio 2010 the Guidance Package Manager is what allows you to Add
"WCF Implementation Projects" and populates the ProjectMapping.xml file.
So how does the ProjectMapping.xml file suppose to get populated in Visual Studio 2012 version?
Do I need to manually edit and create the file?

Does WSSF 2010 Open Source for Visual Studio 2012 REQUIRE that I install:
1) "GAX 2010 for Visual Studio 2012",
   http://visualstudiogallery.msdn.microsoft.com/1412659a-622c-47a4-af1e-a3f75afdd79b  
2) "GAT 2010 for Visual Studio 2012"
   http://visualstudiogallery.msdn.microsoft.com/8d33c4af-4e88-4af7-b411-b20a95954074
3) Microsoft Visual Studio 2012 SDK
 http://www.microsoft.com/en-us/download/details.aspx?id=30668

For Visual Studio 2010 the Requirements are:
To use the Web Service Software Factory 2010, you need the following software installed on your computer:
• Microsoft Visual Studio 2010 (Ultimate, Premium, or Professional)
• Guidance Automation Extensions 2010
• Visual Studio 2010 SDK

Then to install the Service Factory 2010
• Double click the WSSF2010.VSIX file to install the Service Factory.

What are the requirements for Visual Studio 2012 other then the VSIX file Microsoft.Practices.ServiceFactory.Package.vsix ?????

Thanks!
Feb 5, 2014 at 9:10 PM
I had the same problem. I cheated to get around it. I built the solution and the service model using VS2010. Then I opened/converted the solution using VS2012. It worked fine in VS2012 after that.
Feb 5, 2014 at 9:17 PM
Yes, I have done that but I have to imagine when they ported to Visual Studio 2012 they had to have figured this out.
I have been using the WSSF for the last seven years. I am trying to determine how viable this Visual Studio 2012 port is.
See what all of its limitations are. Unfortunately this looks like the last Hurrah for WSSF.
Feb 5, 2014 at 9:20 PM
My Dev team has been using it for about that long too. We like it a lot but, unfortunately, I agree; WSSF seems to be losing its following and may be doomed.
Feb 7, 2014 at 4:01 PM
Ok here is the answer. Cannot believe I did not see this.

If you right click on any "Folder" e.g. "Service Interface" folder and right click you will see
at the top of the menu "Populate Project Mapping Table".

This will indeed automatically populate the Project Mapping Table.

Thanks to "hernandelahitte"