Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Clients Control Add-In...
Microsoft Dynamics NAV (Archived)

Clients Control Add-In does not get updated once deployed

(0) ShareShare
ReportReport
Posted on by PAE_SM 110

Hi!

I really like the feature to autodeploy assemblies from Server to Client. This does work just fine - but only once.

As soon as i update my .dll on the Server & increase it's Version Number it is not automatically deployed to the Client. I have to go to the temporary Add-Ins Folder and Delete them MyPlugin_1.0.0.0 Folder so it downloads MyPlugin_1.1.0.0 Version

Is this even supposed to work that way? Are there any hints or tricks i might try?

 

By the way, i only tried with an visual control add-in so far and i did not fill in the "Version Field" in the Add-In Table. (If i do, it doesn't find the .dll)

*This post is locked for comments

  • Suggested answer
    keoma Profile Picture
    keoma 32,675 on at
    RE: Clients Control Add-In does not get updated once deployed

    fine, that it works.

    to start/stop windows services like the nav service instance you can use the windows tool sc.

    follow technet.microsoft.com/.../bb490995.aspx

  • Verified answer
    PAE_SM Profile Picture
    PAE_SM 110 on at
    RE: Clients Control Add-In does not get updated once deployed

    Ok, so obviously the NAV Service reads it's Add-In Folder only once when starting. If i update an assembly on the Server i do need to restart the instance so it can be properly deployed to the clients and this does indeed work pretty well now.

    I wonder if the Service can somehow be triggered remotly to recheck the assemblies or if they are stored in some table (?)

    Anyways, it works now! Thanks for your assistance jonathan.

  • PAE_SM Profile Picture
    PAE_SM 110 on at
    RE: Clients Control Add-In does not get updated once deployed

    I have a feeling that i need to restart the Nav Service Instance on the Server for it to read in all the current Versions. I will test that and come back with the results.

  • PAE_SM Profile Picture
    PAE_SM 110 on at
    RE: Clients Control Add-In does not get updated once deployed

    it's vb.net actually but i changed it via the Project Property Page and that should have the same effect (it does work once, and the folder is genereated with the proper Version number.)

    the quoted paragraph stated that "you do have to remove the older versions of assemblies that are stored on the client computer".

    I was under the impression that this means "... if you don't want it to grow with old versions" and not "... if you want it to download the newest Version" (which would pretty much render the whole process useless if i have to deal with clients folders anyways (;

  • Suggested answer
    keoma Profile Picture
    keoma 32,675 on at
    RE: Clients Control Add-In does not get updated once deployed

    microsoft citation:

    "To be deployed, an assembly must comply with the following Microsoft Dynamics NAV Server configuration settings: Chuck Size, Max Upload Size, and Prohibited File Types.

    If a .NET Framework interoperability or control add-in assembly is updated and its version number changes, Microsoft Dynamics NAV Server will deploy the updated assembly to the client computer the next time that the client requests the assembly. The updated assembly is put in a subfolder of the %TEMP%\Microsoft Dynamics NAV\Add-Ins folder, where the subfolder has the assembly’s version number as its name. This implementation means that you do have to remove the older versions of assemblies that are stored on the client computer.

    To support compatibility with earlier version of Microsoft Dynamics NAV, before Microsoft Dynamics NAV Server deploys an assembly to a client, the client looks for the assembly in the local Add-ins folder (for example, C:\Program Files (x86)\Microsoft Dynamics NAV\80\RoleTailored Client\Add-ins). If the assembly is not found, then the client will request the assembly from Microsoft Dynamics NAV Server. Javascript-based client add-ins have been using this deployment technique since Microsoft Dynamics NAV 2013 R2.”

    ---------------------

    did you change the version and the file version in source file AssemblyInfo.cs ?

    [assembly: AssemblyVersion("1.0.0.0")]
    [assembly: AssemblyFileVersion("1.0.0.0")]

  • PAE_SM Profile Picture
    PAE_SM 110 on at
    RE: Clients Control Add-In does not get updated once deployed

    I'm not sure if this is related to my problem, but with a DotNet Variable i DO NOT see the most recent version on the Server Tab when searching for my assembly (in my case i see 1.0.0.2 although i already have 1.0.0.4 already running and working).

    When i update an assembly i have to manually change the Version No. in the Subtype string. This does sometimes work - sometimes not.

  • PAE_SM Profile Picture
    PAE_SM 110 on at
    RE: Clients Control Add-In does not get updated once deployed

    I did try with a non visual .net assembly as a DotNet Variable and this does actually work pretty well. But in this case i select the .dll specifically from the Server Tab and it does have the Version in the assembly text.

    Unfortunately i still cant get it to work for a visual control add-in.

  • PAE_SM Profile Picture
    PAE_SM 110 on at
    RE: Clients Control Add-In does not get updated once deployed

    I'm not sure what you mean with "changed entry".

    If i change the Version Number in the AddIn Table (it was blank before) to the version that is already present in the temporary Folder it works. if i delete it from the client folder it does NOT get deployed on next launch (same Version). This also happens when i increase the Version Number and copy the updated DLL to the Server.

    However, even after increasing the Version Number - Nothing changes at the ControlAddIn Property. If i rechoose the AddIn it still says

    "PAENavTools.ArtikelKarteDWFButton;PublicKeyToken=27adae49cf80988d"

    and i dont even need to save and recompile (no changes).

    Am i supposed to see a "Server Tab" when choosing assemblies like i do with a DotNet Variable?

  • Suggested answer
    keoma Profile Picture
    keoma 32,675 on at
    RE: Clients Control Add-In does not get updated once deployed

    no, that won't work.

    first open table "Client Add-in" and check the values of your add-in. change the version number. then go back to field property control-addin and replace the entry by the changed entry. then restart the rtc client.

  • PAE_SM Profile Picture
    PAE_SM 110 on at
    RE: Clients Control Add-In does not get updated once deployed

    Actually i did not. How do i do that? ControlAddIn Property looks like that:

    PAENavTools.ArtikelKarteDWFButton;PublicKeyToken=27adae49cf80988d

    and there is no Version shown or selectable. Can i just add it manually, something like

    PAENavTools.ArtikelKarteDWFButton;PublicKeyToken=27adae49cf80988d;Version=1.1.0.0

    ?

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

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,711 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,458 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans