Errors after deployment

StrataFrame Forum

Errors after deployment

http://forum.strataframe.net/Topic5794.aspx

By Chris Crabtree - 1/12/2007

I used some of the latest goodies (list populating search fields on the BrowseDialog, ThemedContainer window, etc.) on a particular form in my project.

Works fine on my machine (of course!).

But after sending an update out to users to install, the app runs fine on all forms except that particular form with the latest SF stuff.

Specifically, I keep getting MissingMethodException errors, and it looks like its related to the updated controls and possibly the updated version of these same controls not being present on the user machines.

However, I included the latest merge module in the deployment package. I also tried just installing the DLLs directly into the GAC (fails due to lack of strong naming), and finally in desperation just put all the DLLs in the same directory as the EXE. This also fails in exactly the same way as using the merge module. How do I know if I have the right version of this stuff on the client machine?

I included a couple of specific exceptions below. Thanks!

ApplicationException
An error occurred while creating the main form
TargetInvocationException
Exception has been thrown by the target of an invocation.
MissingMethodException
Method not found: 'Void MicroFour.StrataFrame.UI.Windows.Forms.SearchFieldItem.set_PopulationDataSourceSettings(MicroFour.StrataFrame.UI.ListPopulationSettings)'.

Source : MicroFour StrataFrame UI

Stack Trace:
   at ProjectPortfolioManager.ProjectMaintenanceForm.InitializeComponent()
   at ProjectPortfolioManager.ProjectMaintenanceForm..ctor() in C:\Documents and Settings\crabtrjc\My Documents\Visual Studio 2005\Projects\ProjectPortfolioManager\ProjectPortfolioManager\ProjectMaintenanceForm.cs:line 15
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
   at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at MicroFour.StrataFrame.Application.StrataFrameApplication.RunApplication()

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Source : MicroFour StrataFrame UI

By StrataFrame Team - 1/15/2007

I'm not sure, but the file version might change from build to build while the version stays the same. When you attempt to register the SF DLLs in the GAC you said it fails with a strong-name error? It is possible that you might have to completely remove the SF DLLs from the GAC before you re-register them since the version number did not change.

By Chris Crabtree - 1/17/2007

That worked, although terribly inconvenient. I had to have the users:

1. uninstall everything that used SF 1.5 to free up the assemblies for uninstall,

2. uninstall the assemblies,

3. reinstall my application,

4. then reinstall everything else that they uninstalled in step #1.

What would be the downside of incrementing the version for each new...er, version? At least for breaking changes where new methods or properties have been added.

That would prevent this whole scenario, wouldn't it? There must be a tradeoff, of course, although at the moment, after what I've just had to go through, it seems as if that tradeoff couldn't possibly be worth it. Smile

Thanks!

By StrataFrame Team - 1/18/2007

Hehe, yes, I agree with you there... I've had to do the same thing several times. You'll be happy to know that the version of the files will change to 1.5.2 in the next release.