• Login
  • Register

DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Output DotNetNuke.dll library with v.0.0.0

You are not authorized to post a reply.
Sort:


New Member


Posts:13
New Member

    When I compile 'DotNetNuke.Library' project using Visual Studio 2019 through the option in menu 'Build-> Build 'DotNetNuke.Library' there are no errors. The problem that I have is that the out library 'DotNetnuke.dll has version 0.0.0.0 instead of v9.3.0. This technique works for previous DNN versions, but not for DNNv9.3+.

    I also fallowed steps from this tutorial https://github.com/dnnsoftware/Dnn.Platform/blob/develop/.github/BUILD.md , but I got lot's of other errors. 

    I'm missing something obvious, someone can help me?



    Basic Member


    Posts:95
    Basic Member

      The build process has changed a lot since 9.3.0, so it will depend somewhat on what version you're building against. For the latest version (since 9.5.0), you can run ./build.ps1 --target=CreateSettings which will generate a setting.local.json file. In that file, version will be set to "auto", which will use information for the Git repository and branch to determine the version. You can change this to be a specific version (e.g. "9.9.1").  After that's set, ./build.ps1 will do a full build and produce packages in the Artifacts folder that you can use to install a site.

      For older versions I believe you'll want to add version info to SolutionInfo.cs. There's also an AssemblyStatus attribute in DNN Platform/Library/Properties/AssemblyInfo.cs that you may want to change.

      Hope it helps,

      DNN partner specializing in custom, enterprise DNN development https://engagesoftware.com/showcase


      New Member


      Posts:13
      New Member

        Thank you for the detailed answer that put me on the right track!

        If someone will get error message like "Could not download NuGet.exe" after the command "./build.ps1 --target=CreateSettings", please make sure that PowerShell is using correct encryption. For me following code snippet did the trick. 

         try {
            # Set TLS 1.2 (3072), then TLS 1.1 (768), then TLS 1.0 (192), finally SSL 3.0 (48)
            # Use integers because the enumeration values for TLS 1.2 and TLS 1.1 won't
            # exist in .NET 4.0, even though they are addressable if .NET 4.5+ is
            # installed (.NET 4.5 is an in-place upgrade).
            [System.Net.ServicePointManager]::SecurityProtocol = 3072 -bor 768 -bor 192 -bor 48
        }
        catch {
            Write-Output 'Unable to set PowerShell to use TLS 1.2 and TLS 1.1 due to old .NET Framework installed. If you see underlying connection closed or trust errors, you may need to upgrade to .NET Framework 4.5+ and PowerShell v3'

        That I put into the "build.ps1" file, right after line: Write-Host "Preparing to run build script..."

        You are not authorized to post a reply.

        These Forums are dedicated to discussion of DNN Platform.

        For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

        1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
        2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
        3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
        4. No Flaming or Trolling.
        5. No Profanity, Racism, or Prejudice.
        6. Site Moderators have the final word on approving / removing a thread or post or comment.
        7. English language posting only, please.

        Would you like to help us?

        Awesome! Simply post in the forums using the link below and we'll get you started.

        Get Involved