Update Component

[GLMSDev]

Hi,

I have worked on the component and created the app. Now, when I have changed my code and used following commenad..

1. MsBuild /t:restore

2. Msbulid

it generates the zip file. Now, I already have component uploaded. first it does not ask if i want to replace the component. and second new code does not take effect. 

How do i make sure that my code is updated and running in the model driven app ?

[HemantG]

You would need to update the control version in the manifest file. We are working on improving the user experience here as multiple folks have reported this.

There is no override warning as the action of solution import with the updated control version implies the upgrade intent, like all other solution components.

[GLMSDev]

Can you please provide which tag in manifest file ? When I did it threw an error of version not matching and  did not allow me to upload the component.

[HemantG · Accepted solution]

It is following attribute in manifest. 

<control namespace="MyNamespace" constructor="MyControl" version="0.0.1" ...

Note that if there are incompatable changes in the control manifest like say removal/addition of the required property than the import fails. This is because there is no way for the current version configuration to account for the change. For these rare cases, please remove the control from configuration and then uninstall it. 

[mcutchins]

I tried changing the version number and the changes still did not take.  I have to remove the solution (which entails removing the control from each field, form, view, etc. it is associated with) and then import the solution as new.  This is not great from a maintenance perspective as manual changes are tedious and error prone. 

[Anonymous]

@mcutchins This was helpful for me.  I accidentally posted the same topic as you.  This definitely is a lot to just update the component after you make changes to it.

[GregHurlmanMSFT]

If you update your control version *and* the solution version, you should see an update without having to delete the old one first. We recognize this isn't ideal, and are working on a better devloop-deployment story.

[ManishJain]

Which files are you referring to for updating solution version.

Thanks

[ben-thompson]

The file you needed to update the version number in was in the ControlManifest.Input.xml file.

You don't need to do that anymore if you are using the command line to push the controls to your target environment (which is now the recommended approach). 

[GregHurlmanMSFT]

Please note that the CLI "pac pcf push" method is meant for the dev loop only, not for pushes to a production environment. For that, you should manually bump your version, build for release (msbuild /p:Configuration=release), and deploy the ZIP via the web.