M
Mark Olbert
I am posting this message to two newsgroups because I don't know which one covers the issue, and I need to get a quick resolution.
I have a custom license provider (actually, a license framework) that I have used successfully in a number of Framework v1.1
projects. Part of what it does is create an encrypted licx file as an embedded resource that gets added to a VS project. The licx
file (and the lic file, for that matter) simply contain an encrypted xml description of the user's license rights, and the terms of
the license (well, actually it's a reference to a class which defines the general terms of the license, but that's not relevant).
Here's the problem: under v1.1 and VS2003 this all worked great.
But under v2 and VS2005 a build action attempts to compile the licx file...which isn't possible, since it isn't source code.
Needless to say, this causes a problem. Also needless to say, it is a royal pain in the butt to have the behavior of development
tools change that much between releases.
I'm particularly surprised that the build process attempts to compile the licx file since it is clearly marked as "Embedded
Resource", which in other situations that I've worked on means it should just be copied, as is, to the assembly.
A speedy resolution to this problem would be greatly appreciated.
- Mark
I have a custom license provider (actually, a license framework) that I have used successfully in a number of Framework v1.1
projects. Part of what it does is create an encrypted licx file as an embedded resource that gets added to a VS project. The licx
file (and the lic file, for that matter) simply contain an encrypted xml description of the user's license rights, and the terms of
the license (well, actually it's a reference to a class which defines the general terms of the license, but that's not relevant).
Here's the problem: under v1.1 and VS2003 this all worked great.
But under v2 and VS2005 a build action attempts to compile the licx file...which isn't possible, since it isn't source code.
Needless to say, this causes a problem. Also needless to say, it is a royal pain in the butt to have the behavior of development
tools change that much between releases.
I'm particularly surprised that the build process attempts to compile the licx file since it is clearly marked as "Embedded
Resource", which in other situations that I've worked on means it should just be copied, as is, to the assembly.
A speedy resolution to this problem would be greatly appreciated.
- Mark