My guess would be that the assembly is failing to load due to a missing
dependency.
I should point out though, that using RegPkg.exe to register your package
in a deployment/install scenario is not the proper thing to do. It's my
understanding that the RegPkg.exe utility is not redistributable, and you
should avoid self-registration in your retail setup.
RegPkg.exe is very useful for development and test environments, but you
should be relying on the Windows Installer technology to add the necessary
registry keys. RegPkg.exe has a couple of command line switches that will
produce a .REG or .VRG file which can be useful in identifying the keys
you'll need to add, but I would not recommend using it as a way to register
your package outside of a development or test environment.
Sincerely,
Ed Dore [MSFT]
This post is 'AS IS' with no warranties, and confers no rights.
Enrique - 15 Sep 2005 01:44 GMT
Thanks Ed, Actually I was trying in a development scenario but the problem
was a very different thing.
I was using VS Beta2, (no a CTP version), well the exception that I was
getting was “value does not fall within the expected range” after some search
I found that it was a bug, fixed in later CTPs versions, more information
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=53572
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=74594
I was able to fix it doing a performance session, after I could install my
package without any problem.
Thanks.
> My guess would be that the assembly is failing to load due to a missing
> dependency.
[quoted text clipped - 15 lines]
>
> This post is 'AS IS' with no warranties, and confers no rights.