Exception after deployment to Vista-Machine

StrataFrame Forum

Back

Home
»
StrataFrame Application Framework - V1
»
Issues
»
Exception after deployment to Vista-Machine

Exception after deployment to Vista-Machine

Author	Message
Philipp Guntermann	Philipp Guntermann posted 15 Years Ago HOT Topic Details Share Topic
Group: Forum Members Posts: 141, Visits: 263	Hi, my Application raises the following Exception on a Vista Machine. It works with no Problems on my dev machine (XP): The Typeinitializer for COTAS_Kuma.Business_Objekte.Basis.KundenBO has raised an Exception. TypeInitializatzionException The Typeinitialisator for COTAS_Kuma.Business_Objekte.Basis.KundenbO has raised an Exception. TypeLoadException The Type MicroFour.StrataFrame.Business.FieldPropertyDescriptor`1 in the Assembly MicroFour StrataFrame Business, Version=1.6.0.0, Culture=neutral, PublicKeyToken=99fe9917f71608a7 could not be loaded. Source : COTAS_Kuma Strack Trace: at COTAS_Kuma.Business_Objekte.Basis.KundenBO..cctor() at COTAS_Kuma.Business_Objekte.Basis.KundenBO..cctor(IContainer container) at COTAS_Kuma.Präsentation.KundenverwaltungUI.KundenverwaltungFrm.InitializeComponent() at COTAS_Kuma.Präsentation.KundenverwaltungUI.KundenverwaltungFrm..ctor() at COTAS_Kuma.Präsentation.KundenverwaltungUI.KundenverwaltungFrm.getInstanz(TrayApplikation paParentController) at COTAS_Kuma.Controller.Applikation.TrayApplikation.starteKVKundenverwaltung() at COTAS_Kuma.Controller.Applikation.Traymenü.ClickEventHandler(Object Sender, Eventargs e) at System.Windows.Forms.ToolstripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolstripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) ...
	Reply Like 0
Ivan George Borges	Ivan George Borges posted 15 Years Ago Post Details Share Post
Group: StrataFrame MVPs Posts: 1.9K, Visits: 21K	Have you checked your deployment routine to see if you got the proper DLLs added?
	Reply Like 0
Philipp Guntermann	Philipp Guntermann posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 141, Visits: 263	its a clickonce installation. i have included all required assemblies: Einschließen = Incluide Erforderlich = required.
	Reply Like 0
Trent Taylor	Trent Taylor posted 15 Years Ago Post Details Share Post
Group: StrataFrame Developers Posts: 6.6K, Visits: 6.9K	Your deploying the wrong assembly. You are developing on the 1.6.7 beta and deploying an older assembly. That is what the FieldPropertyDescriptor is telling you. This was when we made the change to the BOs to only require a singe field property descriptor instead of one for each strong-typed property.
	Reply Like 0
Philipp Guntermann	Philipp Guntermann posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 141, Visits: 263	so then how do i change it from deploying the old ones ? visual studio collected this information on its own.
	Reply Like 0
Trent Taylor	Trent Taylor posted 15 Years Ago Post Details Share Post
Group: StrataFrame Developers Posts: 6.6K, Visits: 6.9K	Well, look at the path or reference of your assembly in your project. Where is it? If it is in the GAC, then make sure that you have the most recent assemblies in your c:\Program Files\Common Files\MicroFour\StrataFrame folder (which you should). Look at your install, where is it pulling the files from? I know that this has to be the issue, so you might compare paths.
	Reply Like 0
Philipp Guntermann	Philipp Guntermann posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 141, Visits: 263	it seems to me that it deploys the right version. screenshot of files that gets deployed into ../publish/application files: and below a screenshot of the file in my GAC Folder: they both say version 1.6.6.5
	Reply Like 0
Trent Taylor	Trent Taylor posted 15 Years Ago Post Details Share Post
Group: StrataFrame Developers Posts: 6.6K, Visits: 6.9K	Phillip, we can go bacck and forth, but I know that this is your problem. Past getting on your machine and finding the different assmeblies, I am not sure what else to tell you.
	Reply Like 0
Philipp Guntermann	Philipp Guntermann posted 15 Years Ago Post Details Share Post
Group: Forum Members Posts: 141, Visits: 263	Hi, ahem, i am not trying to go back and forth ? It seems to have put the correct assembly file into the "application files" folder, right ? from the screenshot stating it is version 1.6.6.5 ? So i guess that possible vista's security.. stuff.. is preventing the clickonce installation from copying the new included assemblies over the old ones that still reside on the machine ? could that be the cause ?
	Reply Like 0
Trent Taylor	Trent Taylor posted 15 Years Ago Post Details Share Post
Group: StrataFrame Developers Posts: 6.6K, Visits: 6.9K	Yes. If this was a pre-existing machine, then it is entirely possible that the permissions prevented the existing assemblies from being updated. That is a common deployment issue that comes up.
	Reply Like 0