Universal 10 exported solution taking a very long time to build

Target Platforms Desktop
1

Hello,
I recently switched from Windows 8.1 to Universal 10 for my Windows store export and noticed that the build time is now extremely long (from seconds in 8.1 to around 10 minutes in Universal 10)

I’m using Visual Studio 2015 with update 3.

Is there any way to speed up the build time for Universal 10 solutions? Is this a common issue?

Regards

2

No, that is not expected, there shouldn’t be a significant difference, unless you use il2cpp scripting backend.
Have looked into output tab while building, at what part it’s taking long? One thing might be NUget resolving packages, that might take long if you have a very slow internet connection.

3

thank you for your answer,

I’m not using il2cpp

I tried to disable NUGet resolving without noticable differences

It’s seems to be taking long once the build start, below is the output from my last build, lots of warning but I don’t know if they are the cause

4

Oh, no I got it. Yes, Master builds are much slower, because of .NET Native.
For local testing purposes you can disable it in project settings, though you are required to use it for submission to store.

5

thanks for the clarification

maybe you can also help me with my real issue.

I have an instruction looking like this:

if(float >= int)
{
Do something
}

the x86 master build might return true, even if the float is not bigger or equal to the int (e.g. 30f>=50 = true)
debug and x64 builds are working fine

from my investigation here is what I found:

  • if I define the float in my method and cast it as int it will work properly
private void MyMethod()
{
   int l_value = (int)30f;
   if(l_value >= 50)
   {
      //Not reached
   }
}
  • if I use a member of my class float it will not work
public float MyValue;
private void MyMethod()
{
   MyValue = 30f;
   int l_value = (int)MyValue;
   if(l_value >= 50)
   {
      //Reached
   }
}

Note that I was not able to reproduce the issue in a new empty project…

now it’s hard to investigate the issue as I have no logs available in Master and it’s taking an eternity to build the project each time I try something new.

Any help our advice regarding my investigations are more than welcome for my mental health ;D

6

There was a bug (in Microsoft tools) where .NET Native resulted in misbehaving code, but you use Update 3, so you are hitting something else.
Basically try all combinations of these two settings:

  • .NET Native
  • Optimize code

Hopefully your issue is only present when both are enabled, then you can disable code optimization (assuming slightly slower is better than non-working one for you :-)).
You can also try VS2017, maybe the issue is gone there. If not, report a bug to Microsoft.

7

thank you once again! no luck with these settings…

I’ll try installing VS2017