Extensions and add-ins

Avanti

Does anyone have experience using add-ins (dll's) together with extensions? I seem to have a bit trouble adding codeunits to extensions, that are dependant on .Net add-ins..
I have tried adding the dll's to a separate extension, but this doesn't seem to work either.

Does anyone have any advice or guides for this?

EvR

Don't take my word for it because I'm not 100% sure. But I think 2016 extensions are not compatible with custom assemblies. I've heard that in 2017, assemblies will be fully supported.

Can anyone confirm this?

postsaurav

Hi @Avanti ,
I agree what @EvR Said. NAV 2017 Extension will support Custom assemblies.

Read Here - http://saurav-nav.blogspot.in/2016/05/microsoft-dynamics-nav-2016-extensions.html

Wait for 2017 Release and i hope same will be available in 2016 latest CU (After release of 2017). This will be in 2016 is not a guarantee but i Hope that.

Avanti

Thank you for the answers. I Guess I'll have to wait then.. At least it's only for a few weeks (hopefully).

mohana_cse06

Its announced yesterday and you can register for a beta program and get NAV2017 version already.
https://connect.microsoft.com/site687/InvitationUse.aspx?ProgramID=9226&InvitationID=NAV-RKXJ-X24Y

EvR

I can now confirm that it works as promised.
Custom assemblies are fully supported in 2017 extensions. Tested!

wittgenstein

@EvR:
Sorry to bring this old topic up again. But I am struggling with creating an extension with a Client Control Add-In (custom assembly) for NAV2017.

Is there some kind of a tutorial on how to do this? I already tried Google - without success though.

Jan_Veenendaal

In shorthand:
1. Create your control add-in as in earlier versions, including the manifest file and resources in a zip.
2. In the zip-file ALSO include your .dll (in the root of the zip)
3. Put the zip file in your 'delta' folder
4. Create your extension as described here: https://msdn.microsoft.com/en-us/library/mt600264(v=nav.90).aspx

wittgenstein

Awesome. Easier than I thought it would be.
Thanks :-)

DenSter

It would be cleaner to create a separate folder specifically for your add-ins, and then you can include that folder in the -SourcePath parameter when you create the NAVAppPackage in PowerShell

Something like this:

Tihomir

If i keep my zipped .dlls in a folder i seem to allways get error in a format:
Could not find a part of the path 'C:\Users\tihom\AppData\Local\Temp\tmp7122.tmp\SharpSSH.zip
Same if i put them in Delta folder.
If i have single zip in delta folder i get error: Sequence contains more than one element.

I'm using several .dlls projects, so having several zip files containing several .dlls. They are not all control-addins.

Anyone has any experience with this?