VS 2015 Win10 Universal 8.1 target sln error / bug!

Have a fresh install of Windows 10 and VS 2015 installed. Both Unity 5.1.2 and Unity 5.2 beta4 give the error below when trying to build a fresh Universal 8.1 app from Unity3D.

Anyone else hitting this bug? Looks like Unity proj files are bad and VS 2015 is hitting it. While it shouldn’t have this kind of error in VS maybe there is a bug in both VS 2015 and Unity.

Here is the text from the log file:

Did you try creating just an empty project from VS to confirm the installation isn’t borked?

Ya blank Universal 8.1 app created from VS 2015 works and compiles just fine. Only when I open one created from Unity does it mess up.

Win10 Universal apps open fine though when created from Unity (they just don’t build yet as you already know).

Alright, thanks. We’ll look into it.

I’m hitting the same issue. Has there been a solution/work around?

My guess is the fix will be in Unity 5.2, did you try beta 5: https://unity3d.com/unity/beta

Beta 5 has no such fix yet. We’re still trying to reproduce it locally: couldn’t do it on 2 machines already.

A workaround for now would be to install and use VS2013 to build Universal projects, or build Store 8.1 and Phone 8.1. I’ll let you know once we have more details on the issue.

Hey, here’s an update: our QA managed to reproduce it. However, it seems that this error is merely a cosmetic one: pressing build builds the project successfully. Could you confirm it works for you too?

Hi there. I can confirm that this also happens to me and I don’t think this is only cosmetic as the Shared Code project fails to load. I have tried making a clean build and still facing the same issue.
2244843--149911--upload_2015-8-11_2-42-24.png

I’m having the exact same error. Fresh install of Windows 10 and Unity 5.1.2f1 Personal.

Any solution?

Is this the latest VS 2015 RTM ?

I have exactly the same problem as reported above. The frest install of lates Unity 5.1.2f1 Personal and Visual Studio 2015 Community.

As you see in attached file, shared project can’t load (error and log the same as OP has). I checked and I could build a working game and manifests are not shared so a game is somehow possible to be published… but changing some shared scripts for ads control is something I currently seek.

2257545--150930--Przechwytywanie.PNG

Please fill a bug report, and please specify exact VS 2015 version, you can get it from Help->About menu.

I have exactly the same problem,

config:

  • VS 2013 12.0.31101.00 Update 4
  • VS 2015 14.0.23107.0 D14REL
  • Unity 5.1.1f1 Personal
  • Visual Studio 2013 + 2015 Tools

I open the project build on Visual Studio 2013 or 2015, there is the same mistake.
I also recreate the .scproj and .sln in the Unity project

We have also the same issue with unity 5.2.0f3 and visual studio 2015.

At the start up we receive the same error as already mentioned.
The shared project has the status “loading…” and does not change anymore.

Here the exact versions of all installed tools with Vistual Studio:

Microsoft Visual Studio Community 2015
Version 14.0.23107.0 D14REL
Microsoft .NET Framework
Version 4.6.00079

Installed Version: Community

Visual Basic 2015 00322-20000-00000-AA475
Microsoft Visual Basic 2015

Visual C# 2015 00322-20000-00000-AA475
Microsoft Visual C# 2015

Visual C++ 2015 00322-20000-00000-AA475
Microsoft Visual C++ 2015

Windows Phone SDK 8.0 - ENU 00322-20000-00000-AA475
Windows Phone SDK 8.0 - ENU

Application Insights Tools for Visual Studio Package 1.0
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 14.0.20626.0
ASP.NET and Web Tools

ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
For additional information, visit http://www.asp.net/

Common Azure Tools 1.5
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

GenerateUnitTest 1.0
Generates unit test code for methods in classes under test.

Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools

Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers

NuGet Package Manager 3.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

SQL Server Data Tools 14.0.50730.0
Microsoft SQL Server Data Tools

Visual C++ for Cross Platform Mobile Development 1.0
Visual C++ for Cross Platform Mobile Development

Visual C++ for Cross Platform Mobile Development 1.0
Visual C++ for Cross Platform Mobile Development

Visual Studio Tools for Universal Windows Apps 14.0.23121.00 D14OOB
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.

Same situtation on my side - VS 2015, Unity Personal 5.1.1 (x64). Built Project for Windows Store, Universal 8.1 and got this error.

Seems some changes in VS2015 triggers this issue both in VS 2013 and VS 2015.

Anyways, the ones who has this failure, can you try this:

  • open <project>.Shared<project>.Shared.projItems
  • find places like this (MSBuildThisFileDirectory)<file>.xaml</DependentUpon> and remove (MSBuildThisFileDirectory)

For ex.,

<DependentUpon>$(MSBuildThisFileDirectory)App.xaml</DependentUpon>

change to

<DependentUpon>App.xaml</DependentUpon>

and see if that helps

Ok, trying what Tomas1856 mentioned worked half way.
The shared project is loaded now, but the two other projects now have problems - they cannot find the two files app.xaml and mainpage.xaml (which reside in the shared project).

The file “<project>.Windows\App.xaml” could not be found.

Just remove those two lines in *.projItems file of Shared subproject :

$(MSBuildThisFileDirectory)App.xaml

$(MSBuildThisFileDirectory)MainPage.xaml

it looks like these definitions are needed only for visual studio to display cs files as submenu for xaml files. I don’t know why it casues error in visual studio but it’s adding all required files to final project and links them with xaml files without problems.

1 Like

Kroolyk is right, worked for me!