Form customdialog not working for new console extension model

Question

question

PeterSzalatnay asked Jan 28, '22 PeterSzalatnay commented Jan 31, '22

Form customdialog not working for new console extension model

Hi Guys,

I am trying to update ConfigMgr Quick Tools to support the new console extension cab deployment, but have run into issue with the form xml files.

This is the old xml that worked when the extension was located in the AdminConsole\bin folder

<?xml version="1.0" encoding="utf-8" ?>
<SmsFormData FormatVersion="1.0" xmlns="http://schemas.microsoft.com/SystemsManagementServer/2005/03/ConsoleFramework">;
<Form Id="{EE5552EA-25E5-4A27-A20E-621456A63BFD}" CustomData="AddResourcesList" FormType="CustomDialog">
<Assembly Name="ConfigMgr.QuickTools.dll" Namespace="ConfigMgr.QuickTools.CollectionManagment" ClassType="AddResourcesListDialog" />
</Form>
</SmsFormData>

But with the new location of the dll files in AdminConsole\Extensions it throw an error that it cannot find the assembly file. If I add the full assembly path it works fine. But that will not work as installation paths are different for each use.

<?xml version="1.0" encoding="utf-8" ?>
<SmsFormData FormatVersion="1.0" xmlns="http://schemas.microsoft.com/SystemsManagementServer/2005/03/ConsoleFramework">;
<Form Id="{EE5552EA-25E5-4A27-A20E-621456A63BFD}" CustomData="AddResourcesList" FormType="CustomDialog">
<Assembly Name="C:\Program Files (x86)\Microsoft Endpoint Manager\AdminConsole\Extensions\4aacf4b3-86d1-4c83-97e7-f814d22879ae\2.3\bin\ConfigMgr.QuickTools.dll" Namespace="ConfigMgr.QuickTools.CollectionManagment" ClassType="AddResourcesListDialog" />
</Form>
</SmsFormData>

Any suggestion on what the generic assembly path should be?

Cheers

mem-cm-sdk

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 1 · 2022-01-31T06:41:38.49Z

AllenLiu-MSFT answered Jan 31, '22 PeterSzalatnay commented Jan 31, '22

Hi, @PeterSzalatnay

Thank you for posting in Microsoft Q&A forum.

If you are deploying to a directory other than the %ProgramFiles%\Microsoft Endpoint Manager\AdminConsole\bin folder, the form XML<Assembly> attribute, Name, should include the assembly filename and the full path to the file.

For more information, see How to Create Form XML for a Configuration Manager Property Sheet:
https://docs.microsoft.com/en-us/mem/configmgr/develop/core/servers/console/how-to-create-form-xml-for-a-configuration-manager-property-sheet

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PeterSzalatnay · Jan 31 at 08:00 AM

How is this going to be compatible with the new console extensions?

https://docs.microsoft.com/en-us/mem/configmgr/develop/core/servers/console/console-extension-register

We cannot supposed to use the full path as there is nothing in the console extension that will change the path when to user is installing in a different location then %ProgramFiles(x86)%.

Guess they wants us to use the new extensions but none has actually tested that all paths are working. As the action xml can pickup the right assembly even when its in the new AdminConsole\Extensions locations.

0 ·

question