I followed the Crystal Reports and Visual Studio .NET PDF and distributed my
app with all the merge modules. However I came across the usual
keycodev2.dll not found. So I manually registered the file myself and now
all is well.
In itself this isn't too much of a problem on my local network as I threw
that command in the login scripts and now all is well however I cant believe
this is by design. In the future these apps will go outside of our network
and I must solve this issue before then.
Shouldn't the merge modules be registering (or doing whatever they where
intended to do) themselves?
Aside from adding that DLL to my project outside of its merge module is
there some other way of handling this?
Any help would be appreciated, thanks.
