web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Changed DLL reference ...
Microsoft Dynamics AX (Archived)

Changed DLL reference is not getting refreshed in UAT instance

(0) ShareShare
ReportReport
Posted on by Naga Srinivas 5

Hi Everyone,

We have added DLL as reference in D3650 and deployed to UAT as a package from LCS. Later we changed the code in the DLL and added it again deleting the existing one. In development it is working fine, but same when we deployed to UAT it is still pointing to old DLL.

We tried deleting the DLL from UAT bin folder manually and deployed package again but still no use.

Note: We are in implementation phase, so the production is not deployed we have just DEV and UAT.

Any help please.

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 239,040 Most Valuable Professional on at

    Does "still no use" mean that the old versions gets installed from them deployable package? I suggest you explicitly verify it by unzipping the deployable package and checking its content. How did you create the package?

  • Naga Srinivas Profile Picture
    Naga Srinivas 5 on at

    In package it is showing the new DLL only, even we checked the DLL in bin folder of UAT after deployment it is showing new DLL. But when we access the application it is executing same old DLL logic.

    We are creating package from DEV server VS.

  • Martin Dráb Profile Picture
    Martin Dráb 239,040 Most Valuable Professional on at

    Are you saying that the DLL doesn't exist there at all but it's still executed? That's sounds weird. How exactly are you testing it? What if you use reflection to identify the path of the assembly loaded to AX?

    By the way, creating packages from VS isn't reliable enough. You should use a build server to be sure that you're building code from version control, not from code that happen to lie on a DEV box (which doesn't have to be in sync with version control).

  • Community Member Profile Picture
    Community Member on at

    Hi Srinivas,

    Delete all references from Visual Studio first. Try to rebuild same. If you are not getting any error that means it is still referencing somewhere.

    Now go to My computer and try to search dll with keyword. Delete all files which you find over there.

    Now rebuild the project you will definitely get error.

    Copy Paste new DLL in VM and give reference again. Rebuild project.

    Regards,

    Smit

    Remember to delete every copy of DLL from VM once you change Latest DLL.

  • Martin Dráb Profile Picture
    Martin Dráb 239,040 Most Valuable Professional on at

    I think that looking at Assembly.Location property is better than searching the whole computer for DLLs and guessing which one is actually used. Also, don't forget that assemblies may be in Global Assembly Cache (I don't know whether it may be the case here or not, because Naga hasn't provided such information.

    Naga, I assumed you restarted IIS. Please do it if not.

  • Naga Srinivas Profile Picture
    Naga Srinivas 5 on at

    Hi Smit,

    I have already tried the above way, when I deleted the reference try to rebuild it is throwing error and it is working perfectly in DEV environment, only problem is in UAT.

    As VS is not available in UAT I cannot do the same in UAT.

  • Naga Srinivas Profile Picture
    Naga Srinivas 5 on at

    Hi Martin,

    As we have only one DEV sandbox, we are creating package directly from DEV box.

    We have checked the GAC with GACView tool also but we did't found our assembly registered there. Also we restarted IIS after every deployment.

  • Martin Dráb Profile Picture
    Martin Dráb 239,040 Most Valuable Professional on at

    Wait, are you building the application from source code in UAT? I thought you said you're deploying a deployable package, not source code. Please elaborate what exactly you did and what error you got.

    By the way, if your assembly doesn't have a strong name, don't bother looking to GAC.

  • Naga Srinivas Profile Picture
    Naga Srinivas 5 on at

    Yes, we are deploying as a package only not source code.

    We are building in DEV server and taking the package and deploying it to UAT from LCS.

  • Martin Dráb Profile Picture
    Martin Dráb 239,040 Most Valuable Professional on at

    Then I have no idea what you were referring to in "when I deleted the reference try to rebuild it is throwing error and it is working perfectly in DEV environment, only problem is in UAT".

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Andrew Jones a1x Profile Picture

Andrew Jones a1x 2

#3
GL-01081504-0 Profile Picture

GL-01081504-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans