How to bypass warnings when targeting .Net 4.5.2 during publish

Question

My Azure services target .Net 4.5.2 and run fine in dev. However, build produces the warning(s):

Warning The project 'SurfInfoWeb' targets .NET Framework 4.5.2. To make sure that the role starts, this version of the .NET Framework must be installed on the virtual machine for this role. You can use a startup task to install the required version, if it is not already installed as part of the Microsoft Azure guest OS.

I believe these (local) warnings are causing the publish to fail immediately (and these are the ONLY warnings in the error list).

According to MS, 4.5.2 is supposed to be available in January 2016 (I'm not sure exactly what date, but I thought I had read Jan 12 or Jan 16).

I can't suppress these warnings in the normal way because they don't have warning codes.

1) Is .Net 4.5.2 actually available on Azure

2) Is there a way to suppress warnings that don't have codes?

3) Something else I'm not thinking of?

I'm using SDK 2.8.1. And OSVersion="*".

Answer 1

Is .Net 4.5.2 actually available on Azure?

Yes. .NET 4.5.2 is available in the current osVersion * of osFamily 2, 3 and 4.

Is there a way to suppress warnings that don't have codes?

Cloud service projects upgraded to Azure SDK 2.9 no longer generate this warning. Projects using a prior version of the SDK (even if version 2.9 is installed) still generate this warning. To suppress this warning without upgrading the project to SDK 2.9 you can add the following snippet to your .ccproj file.

<ItemGroup> <WindowsAzureFrameworkMoniker Include=".NETFramework,Version=v4.5.2" /> </ItemGroup>

Answer 2

Based on the comments provided here - https://azure.microsoft.com/en-in/documentation/articles/cloud-services-dotnet-install-dotnet/, there's no way to suppress this warning.

Is .Net 4.5.2 actually available on Azure?

As of today, yes. .Net 4.5.2 is available on Azure. In fact, we ported our solution from .Net 4.5 to .Net 4.5.2 just a few days ago.

In order to make use of .Net 4.5.2, you can't use "*" for osVersion. You would need to target a specific OS version. Please see the Guest OS/Target Framework version matrix here: https://azure.microsoft.com/en-in/documentation/articles/cloud-services-guestos-update-matrix/.

Our solution makes use of osFamily 4 and based on this matrix, we ended up using WA-GUEST-OS-4.26_201511-02 osVersion. Here's how our service configuration file looks like:

<?xml version="1.0" encoding="utf-8"?>
<ServiceConfiguration serviceName="ServiceName" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" osFamily="4" osVersion="WA-GUEST-OS-4.26_201511-02" schemaVersion="2015-04.2.6">
  <Role name="RoleName">
  </Role>
</ServiceConfiguration>

Answer 3

I'm getting a similar version of this error, essentially, the new version of it:

Microsoft Azure Cloud Service projects only support roles that run on .NET Framework versions 4.0, 4.5 and 4.6. Please set the Target Framework property in the project settings for project 'MyWorkerRole' to .NET Framework 4.0, .NET Framework 4.5 or .NET Framework 4.6.

And

The project 'MyWorkerRole' targets .NET Framework 4.7.2. To make sure that the role starts, this version of the .NET Framework must be installed on the virtual machine for this role. You can use a startup task to install the required version, if it is not already installed as part of the Microsoft Azure guest OS. For more details, see https://go.microsoft.com/fwlink/?LinkId=309796.

Even after following the directions located at the link in the message (which were helpful in creating the installer scripts, etc.), the warning message did not go away. I tried all sorts of stuff including the framework moniker item groups, all kinds of properties, etc.

Ultimately, I ended up turning my build on Detailed output, figured out the .targets file this was coming from and inspected it. -- I found that there is just no built-in way to suppress it.

HOWEVER, there is a hack you can do -- I basically copied that block from the .targets file into my .ccproj file, and removed the part about the warning. Basically I added the following to the end of my .ccproj file, and BADAO!, just like that NO MORE WARNINGS!:

<Target Name="ValidateRoleTargetFramework"
        Outputs="%(RoleReference.Identity)"
        Condition="'@(RoleReference)' != ''">

  <PropertyGroup>
    <_RoleTargetFramework>%(RoleReference.RoleTargetFramework)</_RoleTargetFramework>
    <_IsValidRoleTargetFramework>False</_IsValidRoleTargetFramework>
    <_IsValidRoleTargetFramework
      Condition="$(_RoleTargetFramework.StartsWith('v4.0')) Or $(_RoleTargetFramework.StartsWith('v4.5')) Or $(_RoleTargetFramework.StartsWith('v4.6'))">True</_IsValidRoleTargetFramework>
  </PropertyGroup>

</Target>

(Obviously, you should put that INSIDE your <Project /> tag, of course.)

Answer 4

You should to install .net 4.5.2 on webrole virtual machine.

Download the the web installer for the .NET framework you want to install .NET 4.5.2 Web Installer

For a Web Role

1. In Solution Explorer, under In Roles in the cloud service project right click on your role and select Add>New Folder.
2. Create a folder named bin Right click on the bin folder and select Add>Existing Item. Select the .NET installer and add it to the bin folder.
3. Define startup task for your role ServiceDefinition.csdef <LocalResources> <LocalStorage name="NETFXInstall" sizeInMB="1024" cleanOnRoleRecycle="false" /> </LocalResources> <Startup> <Task commandLine="install.cmd" executionContext="elevated" taskType="simple"> <Environment> <Variable name="PathToNETFXInstall"> <RoleInstanceValue xpath="/RoleEnvironment/CurrentInstance/LocalResources/LocalResource[@name='NETFXInstall']/@path" /> </Variable> </Environment> </Task> </Startup>
4. Create a file install.cmd and add it to role by right click on the role and selecting Add>Existing Item.

install.cmd

```

REM Set the value of netfx to install appropriate .NET Framework. 
REM ***** To install .NET 4.5.2 set the variable netfx to "NDP452" *****
REM ***** To install .NET 4.6 set the variable netfx to "NDP46" *****
REM ***** To install .NET 4.6.1 set the variable netfx to "NDP461" *****
set netfx="NDP46"

REM ***** Needed to correctly install .NET 4.6.1, otherwise you may see an out of disk space error *****
set TMP=%PathToNETFXInstall%
set TEMP=%PathToNETFXInstall%

REM ***** Setup .NET filenames and registry keys *****
if %netfx%=="NDP461" goto NDP461
if %netfx%=="NDP46" goto NDP46
    set netfxinstallfile="NDP452-KB2901954-Web.exe"
    set netfxregkey="0x5cbf5"
    goto logtimestamp

:NDP46
set netfxinstallfile="NDP46-KB3045560-Web.exe"
set netfxregkey="0x60051"
goto logtimestamp

:NDP461
set netfxinstallfile="NDP461-KB3102438-Web.exe"
set netfxregkey="0x6041f"

:logtimestamp
REM ***** Setup LogFile with timestamp *****
set timehour=%time:~0,2%
set timestamp=%date:~-4,4%%date:~-10,2%%date:~-7,2%-%timehour: =0%%time:~3,2%
md "%PathToNETFXInstall%\log"
set startuptasklog="%PathToNETFXInstall%log\startuptasklog-%timestamp%.txt"
set netfxinstallerlog="%PathToNETFXInstall%log\NetFXInstallerLog-%timestamp%"

echo Logfile generated at: %startuptasklog% >> %startuptasklog%
echo TMP set to: %TMP% >> %startuptasklog%
echo TEMP set to: %TEMP% >> %startuptasklog%

REM ***** Check if .NET is installed *****
echo Checking if .NET (%netfx%) is installed >> %startuptasklog%
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release | Find %netfxregkey%
if %ERRORLEVEL%== 0 goto end

REM ***** Installing .NET *****
echo Installing .NET: start /wait %~dp0%netfxinstallfile% /q /serialdownload /log %netfxinstallerlog% >> %startuptasklog%
start /wait %~dp0%netfxinstallfile% /q /serialdownload /log %netfxinstallerlog% >> %startuptasklog% 2>>&1

:end
echo install.cmd completed: %date:~-4,4%%date:~-10,2%%date:~-7,2%-%timehour: =0%%time:~3,2% >> %startuptasklog%

```

You can get the full detailed procedures here:

Install .NET on a Cloud Service Role

I think you should implement this workaround until Azure full support .net 4.5.2 may be is not yet supported in your region.Try creating a new cloud instance in EastUS to test if net fx 4.5.2 is already supported.