G
Guest
Hi,
I'm trying to prepare to use IsolatedStorage with an app that is going to
become a clickonce app. From what I understand, you can use the "application"
scope instead of the "assembly" scope in order to have differing assembly
versions not result in separate storage. Is this correct?
Q1: What does the "assembly" scope refer to? What info does it base this off
of? I tried to sue assembly scope and then change the version and rerun, but
I was accessing the same store. Then I found a blog that seemed to indicate
that you need to sign your assembly to have it use the version number. Is
this correct? If so, then is application mode the same as assembly mode for
unsigned assemblies?
Q2: When using "application" mode, I got:
Unable to determine application identity of the caller.
I read that this is because this mode can only be used when you're using a
clickonce app. If so, what's an elegant solution that would allow for
debugging locally?
Thanks...
-Ben
I'm trying to prepare to use IsolatedStorage with an app that is going to
become a clickonce app. From what I understand, you can use the "application"
scope instead of the "assembly" scope in order to have differing assembly
versions not result in separate storage. Is this correct?
Q1: What does the "assembly" scope refer to? What info does it base this off
of? I tried to sue assembly scope and then change the version and rerun, but
I was accessing the same store. Then I found a blog that seemed to indicate
that you need to sign your assembly to have it use the version number. Is
this correct? If so, then is application mode the same as assembly mode for
unsigned assemblies?
Q2: When using "application" mode, I got:
Unable to determine application identity of the caller.
I read that this is because this mode can only be used when you're using a
clickonce app. If so, what's an elegant solution that would allow for
debugging locally?
Thanks...
-Ben