ok. thanks.

That is an question for someone who uses ClickOnce.  We do not use or support ClickOnce due to many issues (not unlike this one) that we ran into early on.  We use InstallAware for all of our distribution.  There are most likely a lot of blogs on the web that might be able to give you an idea here.

Allright. i guess thats the isse then. The Application also threw an error when the trying to save something to the registry in the security editor.

Now, how would i go to enable the clickonce file to get the required permissions ?

Thanks.

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.

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 ?

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.

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

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.

so then how do i change it from deploying the old ones ? visual studio collected this information on its own.

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.