As most architects know, this has been possible for a few years by manually baking your own MSBuild files. The heavy cost with this technique is keeping teams inline with the churn; often updating the builds gets missed.
Thanks for pulling this close to the VS experience. This makes a huge difference to many project roles.
I am trying to add this extension to visual studio 2013 premium. I have tried multiple times with restarting visual studio, but i still get same following error.
"The 'SAPReferenceManagerPackage' package did not load correctly."
Any help for solving this issue is greatly appreciated.
first of all, thank you very much for this extension. Shared projects make my life so much easier. For now I just use them with universal apps. With this extension I had hoped to use it in the largest of my apps to make some things a lot easier than I currently do with PCLs.
However, I'm running into a lot of issues. Mainly Visual Studio freezes and compiler issues.
I can see that the last update on this happened on April 18th. Any chance for an update here soon?
I'd also be willing to send you my whole code so that you can have a look. For now, I don't want to try out VS 14 CTP as it is not recommended for production plus I think that WP is not supported 100% yet.
From reading earlier posts I thought Update 3 added support for creating new shared projects from Add Project - that there was a template for Class Library (Shared). I installed VS 2013.3 RTM today and I can find no template that looks remotely like a shared class library.
Does that mean I should download the Shared Project Reference Manager? Am I being particularly blockheaded by not seeing something?
Just saw a problem with embedded resources as Pages and Resource Dictionary. If we check with ILSpy for example, we can see that paths are not included.
A page under the directory /Pages/MyPage/MyPage.xaml will be saved under mypage.xaml and not pages/mypage/mypage.xaml, so MergeDictionary as well as navigations will failed
Tested with a Windows Phone Silverlight 8.0 project
Could you give us some more details about the issue you are seeing? I have been unable to reproduce this issue, so if you could provide what steps you took leading to the issue, that would be helpful.
I can reproduce this. At the moment it makes sharing XAML content within a nested directly structure impossible.
Create a WP 8.0 or 8.1 project.
Create a shared project and reference it in the WP project.
Create a UserControl or Page (.xaml) in a nested directory and use it somewhere. It breaks.
If you open the assembly in Reflector, the .XAML files are placed at the root and not in the nested directory.
Visual Studio “14” CTP2 was just released. You can download it from the following link for free:
One of the technology improvements in this release is Shared Projects. After installing this CTP2:
• Shared project references can be managed (added or removed) via the Reference Manager dialog, just like Project to Project references.
• Shared Project referencing is also available for some Desktop C# projects. The project types and languages that support Shared Projects will continue to expand in future CTPs.
If you’re interested in how the Shared Project features are evolving in Visual Studio 14, please give it a try. Your feedback and comments are welcome. We appreciate your help!
NOTE: this is a very early CTP, so please install in a test environment.
Please refer to http://support.microsoft.com/kb/2967191/en-us for known issues.
The recommendation is to install Visual Studio "14" CTP2 in a VM, a fresh computer, or another non-production test-only machine that does not have Visual Studio 2013 on it.
I'd love to start using Shared Projects but as I understand it they require a Windows 8.1 developer license. Is this true? If so, why? This seems like a great general-purpose code sharing mechanism (a big improvement over linked files). Are there any plans to make them available to those of us who aren't building Store apps?
Or am I completely wrong about all of this?
I'm trying to use Shared Folders in the following solution structure:
- Web application project
- Shared Folder containing HTML, JS and CSS files
... so I would like all of the HTML, JS and CSS in the Shared Folder to be copied to the first three projects in the solution. It works fine between the Windows and Windows Phone apps, but not the web application.
For the web application, I see empty folders created and no html/js/css brought down.
Do Shared Folders work for web apps? Any ideas on what is wrong?
I'm trying this with an existing project where we share code between .NET 4.0 on the desktop and .NET 3.5 CF on CE. I moved some shared C# source files to the Shared project and tried to "add shared project reference" from my .NET 4.0 class library project but nothing happens. Is this supposed to work on generic projects?
My installation is currently absent the CF/CE tooling, and I can confirm that it does work with a desktop .NET 4.0 class library.
However since you're using CF/CE I've started the download of what I hope are the required SDK components.
Can you give me a few more details on what you have in your setup so that I can try to reproduce the problem.
I will fix this if I can!
I hadn't even gotten to trying this with CE/CF but we would be using Windows Embedded Compact 2013 - the recent update that integrates it into VS 2013. I think I found the issue I was having on the .NET 4.0 desktop class lib. In order to build for both FF and CF, we import a customized version of the C# targets instead of the default one (this simply allows for both a Foo.csproj and a Foo_CF.csproj in the same source folder to output to separate bin_FF and bin_CF directory structures). Once I replaced our customized C# targets import with the standard C# targets, the shared project reference manager dialog appeared (where it didn't before). The other thing I worry about (but doesn't appear to be a problem) is that we have been pulling/porting these C# project files forward since VS 2005.
It would be great to have this working with WEC 2013 as the Shared Project approach is much better than our current hack. :-)