I have 10 assembly used in my SCSF application.
I run ngen first for the shell.exe of my application and then the 10 assembly(dll’s).

Am I following the correct process?

Please guide if incorrect.

Thanks,

Sakshi

You’ve been kicked (a good thing) - Trackback from DotNetKicks.com…

Unfortunately ClickOnce application deployment does not support Ngen. Check this article for more information:

Application Startup Time

However, you can use another deployment mechanism like regular Windows Installers to run Ngen after deploying your application.
I also found this article that deals with the same question. I didn’t try it, but perhaps you could find it useful:

Is it possible to use NGen with ClickOnce deployment?

Hope it helps.
Mariano Converti

thanks for this article! Is it also possible to use ngen, if you are deploying a scsf based application via clickonce?

The Version, Culture and PublicKeyToken fields are not required in your ProfileCatalog.xml.
In Addition, if your assemblies’ are not signed with a strong name, the Version field is ignored.

Hope it helps
Mariano Converti

One thing though, we compile some of the modules as part of our application, so the build number changes on each build and we have to manually update the profilecatalog to keep the version attribute up to date. This is the only drawback in comparison with the previous version that uses LoadFrom, there was no need to specify version attribute when you load from using only the assembly name.

This assembly was set as a project reference and copied over to the bin directory each time the solution builds. Now each time the solution builds we should update the profilecatalog.

Are we missing something or is there a way to automate the module build version?

Note: our deployment script uses ngen update to update the assembly native image each time we deploy the module.