S
Shaun Ram
Hi, I have a certain problem & looking for some suggestion please:
1. I created DLL (Class Libraries Managed code)using VB.NET which are
deployed onto the client.
2. If the client encounters a problem, in order for them to realize if
it was a problem with the DLL or their coding they ask for the source
code of my DLL for project reference & debugging, which I can't release.
Is there a way I could send in a debug build, or some reference where
the client could debug through the component, & not have the source code
too.
What is the prescribed Microsoft Best Practice to debug in the client
machine, or troubleshoot.
If I want to implement Debug Symbols into my code, is there any help or
documentation.
Kindly suggest me the best practice for this situation.
Thanking you
Shaun
1. I created DLL (Class Libraries Managed code)using VB.NET which are
deployed onto the client.
2. If the client encounters a problem, in order for them to realize if
it was a problem with the DLL or their coding they ask for the source
code of my DLL for project reference & debugging, which I can't release.
Is there a way I could send in a debug build, or some reference where
the client could debug through the component, & not have the source code
too.
What is the prescribed Microsoft Best Practice to debug in the client
machine, or troubleshoot.
If I want to implement Debug Symbols into my code, is there any help or
documentation.
Kindly suggest me the best practice for this situation.
Thanking you
Shaun