Home/ Questions/Q 786601
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T21:04:06+00:00

I have a project I recently upgraded to VS2010 – the project/solution files are

  • 0

I have a project I recently upgraded to VS2010 – the project/solution files are updated, but I’m still targeting .NET 3.5.

Until now, my standard NAnt build script has not given me any trouble. However, it appears that after updating the project, and updating the NAnt config to be aware of the new tooling, I am now receiving an error when autogenerating assembly information, which fails the build. The relevant build task is below:

<asminfo output="${dir.src}\${file.commonAssemblyInfo}" language="${project.codeLanguage}">
    <imports>
        <import namespace="System.Reflection" />
    </imports>
    <attributes>
        <attribute type="AssemblyVersionAttribute" value="${project.fullversion}" />
        <attribute type="AssemblyFileVersionAttribute" value="${project.fullversion}" />
        <attribute type="AssemblyInformationalVersionAttribute" value="${project.fullversion}" />
        <attribute type="AssemblyCopyrightAttribute" value="${assembly.copyright}" />
        <attribute type="AssemblyCompanyAttribute" value="${assembly.company}" />
        <attribute type="AssemblyConfigurationAttribute" value="${project.config}" />
        <attribute type="AssemblyTrademarkAttribute" value="${assembly.trademark}" />
        <attribute type="AssemblyProductAttribute" value="${assembly.product}" />
    </attributes>
</asminfo>

The error is highlighted for the first line of the asminfo task. It reads:

AssemblyInfo file ‘C:\Users\Grant\Projects\VisualStudio\Checklist\src\CommonAssemblyInfo.cs’ could not be generated.
This method implicitly uses CAS policy, which has been obsoleted by the .NET Framework. In order to enable CAS policy for compatibility reasons, please use the NetFx40_LegacySecurityPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information.

I’ve gathered so far that this is something new to .NET 4. Has anyone had to address this error before? Does anyone know what it is about asminfo that may be triggering the error?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I believe I figured it out. It turns out that some security aspects of the framework were changed, which the new tooling takes into account, but which the older version of NAnt does not (was using 0.85).

    I updated my NAnt using the latest nightly from the NAnt site (0.91 is in beta, has .NET 4 support), reran my build, and it worked. I had to fix a separate issue, but the build is now working.

    • 0