BuyLog In
Ticket T681650
Visible to All Users
Duplicate

We have closed this ticket because another page addresses its subject:

OBSOLETE - XAF Nuget Packages

Missing name spaces from self made Nuget packages

created 6 years ago (modified 6 years ago)

This is a correction to my question here.

It seems that the nuget feed I made is missing some code for the DevExpress.ExpressApp.DC Namespace.

Thus I think I must have missed pushing a .nupkg file I need.

How do I determine which one?

to be continued…

Sign in to comment on this post

Answers approved by DevExpress Support

created 6 years ago (modified 6 years ago)

Hey @kirsten!
When working with nuget.packages you need to reference them via nuget as well. Thats the reason why it did not work in the first place.

Some changes i made:

  1. Added the nuget.config file in the root of the project to tell nuget where to find the additional nuget source. See nuget-config-file for more information. - You will need to adapt the source to target at your private nuget feed.
  2. Changed the existing packages.config references to use the new PackageReference feature of VS2017. See migrate packages config for more information.
  3. Changed all the csproj files to use the new PackageReference based on the nuget packages. Seeinstalling packages for more.

You didn't include your web.config file, so i couldn't test anything, but i hope this will solve your problem.

Note: If you use nuget it's likely you may loose designer support and have additional problems with GAC-references if you work on the project. So basically you need to check everytime you check in if you didn't reference anything out of the GAC, and replace them with PackageReferences by hand in the csproj file.
This is a rather advanced topic, and if you don't really need it, avoid it. You can consider installing the appropriate DevExpress version on a custom agent instead. That is especially easier if you don't need to support multiple patch versions of DevExpress at once.

I hope that makes things a little bit clearer.
Greetings Manuel

    Show previous comments (4)
    KG KG
    kirsten greed 6 years ago

      Also once I had SSL working for the deployed app, I had trouble running the app in localhost.
      but got it working here

      KG KG
      kirsten greed 6 years ago

        The references change to looking like this

        Andrey K (DevExpress Support) 6 years ago

          Hello,

          To help you better manage build processes for your XAF projects and employ CI/CD tools approved within your Enterprise (such as Azure Pipelines), DevExpress NuGet Gallery includes packages based on XAF assemblies in v18.2. You can configure NuGet package restoring with your feed URL, setup Visual Studio's NuGet Package Manager, and install appropriate packages as described in the XAF Nuget packages KB article.
          We appreciate any thoughts you post to the comments section below, but it would also help us if you could answer one question in this survey.

          Thanks,
          Andrey

          Sign in to comment on this post

          Other Answers

          created 6 years ago (modified 6 years ago)

          Hello Kirsten,

          >>It seems that the nuget feed I made is missing some code for the DevExpress.ExpressApp.DC Namespace.
          As I noted in your previous thread (T681058), it is difficult to provide precise comments without a small sample with custom Nuget packages where you see these errors.

          The https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/cs0234 compiler error indicates that required assemblies are missing. In addition to the DevExpress.ExpressApp and DevExpress.Persistent.BaseImpl assemblies, you can also check if DevExpress.ExpressApp.Xpo and DevExpress.Persistent.Base are in place. In general, comparing your Nuget assemblies list with the assemblies list used in a newly created XAF app may help as well.

          If you need to determine all assemblies that include the nested DevExpress.ExpressApp.DC.XXX  namespaces, search the XAF source code by the "namespace DevExpress.ExpressApp.DC", "namespace DevExpress.ExpressApp.Persistent", "namespace DevExpress.ExpressApp" and other suitable strings.

            Comments (3)
            KG KG
            kirsten greed 6 years ago

              >>  In addition to the DevExpress.ExpressApp and DevExpress.Persistent.BaseImpl assemblies, you can also check if DevExpress.ExpressApp.Xpo and DevExpress.Persistent.Base are in place

              are all there.

              I did run the assembly deployment tool and cross checked that everything it mentioned was in the package feed.

              KG KG
              kirsten greed 6 years ago

                >> In general, comparing your Nuget assemblies list with the assemblies list used in a newly created XAF app may help as well.

                Checking

                MG MG
                Manuel Grundner 6 years ago

                  @kirsten
                  Can you upload a sample project? I think you just missed some packages to install.

                  Sign in to comment on this post

                  Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

                  Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.