none
x64 .Net 3.5 Project producing nlp files in build RRS feed

  • Question

  • I am building an x64 project targeting .net 3.5. I get a whole bunch of .nlp files in the build result:

    big5.nlp
    bopomofo.nlp
    ksc.nlp
    mscorlib.dll
    normidna.nlp
    normnfc.nlp
    normnfd.nlp
    normnfkc.nlp
    normnfkd.nlp
    prc.nlp
    prcp.nlp
    sortkey.nlp
    sorttbls.nlp
    xjis.nlp
    

    If I target .net 4.6 instead, I don't get these files. Does anyone know what is going on, and how do I stop these files being produced? Thanks.

    Friday, February 23, 2018 7:37 AM

All replies

  • Hello,

     

     What do you mean "get a whole bunch"? Where are you seeing this listing? As far as

    I know, those files are part of \Windows\WinSxS\x86_mscorlib_ directory from Net 2

    installation. Need more information.

     

     Thanks :)

    Friday, February 23, 2018 10:01 AM
  • I am getting them in my project output bin directory. This doesn't happen if I target the project for .net 4.6 or target the platform for x86.

    I have just tested targeting ".net 3.5 client profile". The problem doesn't happen with that. Maybe my .net 3.5 is broken?

    • Edited by Dev10110110 Friday, February 23, 2018 12:50 PM
    Friday, February 23, 2018 12:44 PM
  • Hello Dev10110110,

    I try to build projects with your conditions but nothing happens. When I was using low version .Net framework the output console will show the warning and other thing works still.

    I agree with ilivewithian's reply.

    >>After a bunch more digging around I noticed that the build server had the .Net framework on, but not the framework SDK. After installing the SDK on the build server the additional assemblies were no longer added.<<

    maybe you need try to install framework SDK and check if it works well.

    Hope this would be helpful.

    Best regards,

    Neil Hu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Saturday, February 24, 2018 9:50 AM
    Moderator
  • Ok, this issue caused me to rip my PC apart. Now I am running a brand new install of Windows 10 Pro x64, with a brand new license, on a brand new disk partition, with a brand new install of Visual Studio 2017 Community. I enabled .net 3.5 through Control Panel -> Program and features.

    All that made no difference. So what am I supposed to install to change this? The 230MB .net3.5 (dotnetfx35.exe) package cannot be installed, because I presume it is already part of the system. It just immediately exited with no warning and no error.

    Briefly I contemplated I suffered from madness, so I created a new and blank c# forms app targeting .net3.5 and x64, and this was what I got:

    C:\Users\[xxxx]\Desktop\WindowsFormsApp1\WindowsFormsApp1\bin\Release>dir
     Volume in drive C has no label.
     Volume Serial Number is [xxxxxxx]
    
     Directory of C:\Users\[xxxx]\Desktop\WindowsFormsApp1\WindowsFormsApp1\bin\Release
    
    24/02/2018  17:34    <DIR>          .
    24/02/2018  17:34    <DIR>          ..
    28/09/2017  15:49            66,728 big5.nlp
    28/09/2017  15:49            82,172 bopomofo.nlp
    28/09/2017  15:50           116,756 ksc.nlp
    28/09/2017  15:50         4,571,136 mscorlib.dll
    29/09/2017  13:43            59,342 normidna.nlp
    28/09/2017  15:50            45,794 normnfc.nlp
    28/09/2017  15:50            39,284 normnfd.nlp
    28/09/2017  15:50            66,384 normnfkc.nlp
    28/09/2017  15:50            60,294 normnfkd.nlp
    28/09/2017  15:50            83,748 prc.nlp
    28/09/2017  15:50            83,748 prcp.nlp
    28/09/2017  15:50           262,148 sortkey.nlp
    28/09/2017  15:50            20,320 sorttbls.nlp
    24/02/2018  17:34             6,144 WindowsFormsApp1.exe
    24/02/2018  17:33               157 WindowsFormsApp1.exe.config
    24/02/2018  17:34            19,968 WindowsFormsApp1.pdb
    28/09/2017  15:50            28,288 xjis.nlp
                  17 File(s)      5,612,411 bytes
                   2 Dir(s)  26,209,157,120 bytes free

    Although, I got nowhere after the hassle of bricking my PC, at least my non-madness has been confirmed.








    • Edited by Dev10110110 Saturday, February 24, 2018 6:05 PM
    Saturday, February 24, 2018 5:50 PM
  • Hello,

     I am not sure what is going on with your build. I am using Win7

    Community 2017 and compiled a simple WinForm configured for

    Net 3.5, x86 and x64. Nothing special about the project.

     It just reads the files in a directory and places them into an object 

    container type ListBox on event handler Load. In the x86 build

    did not get any output like yours but x64 project directory does

    contain files with extension "nlp". Very odd and interesting issue.

     I have, after more research, found that those files are listed as

    part of some security update in Net 3.5 and more for Win7 above

    on x64 target.

     

     Ref: https://social.msdn.microsoft.com/Forums/en-US/c0620f99-4947-44a9-8063-03de2a7a4a5b/x64-net-35-project-producing-nlp-files-in-build?forum=csharpgeneral

     

     Sorry, can not help :/

    • Edited by User3DX Saturday, February 24, 2018 7:20 PM corrected
    Saturday, February 24, 2018 7:01 PM
  • A second best solution is if someone could tell me if the nlp+dll files are needed. If I don't include those files, will my final product crash and burn on the end-user's system?

    A second second-best solution is if someone can tell me whether targeting .net 3.5 Client Profile is just as good targeting .net 3.5? If I target .net 3.5 Client Profile, will I have a greater chance of the final product failing?

    Saturday, February 24, 2018 7:45 PM
  • Hello Dev10110110,

    Sorry for delay reply.

    As far as I search, MSDN doesn't provide detailed info to introduce .nlp file. I'm not sure if the file is necessary needed. The most easiest validating way is try to delete these file and checked if works well.

    There are some description about .nlp file and you could refer it.

    https://social.msdn.microsoft.com/Forums/en-US/adfe9738-4f7e-4e42-81ae-d923a49787a6/icorprofiler-loaded-a-module-with-a-nlp-extension?forum=netfxtoolsdev

    Hope this would be helpful.

    Best regards,

    Neil Hu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, March 5, 2018 12:58 PM
    Moderator