By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,101 Members | 1,387 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,101 IT Pros & Developers. It's quick & easy.

Memory leak and external DLL

P: 4
Hi there,
I have an external DLL (written in VB.NET) that I've created that has few classes with few public shared functions in each class.

I call these function from my website in the following way (example):

mydll.clsCookies.getCookieValue(param1, "param2", "param3")

Because the functions at the dll are shared, I do not have to create an instance of the class first. I assumed that they exist at the application level and do not have to be destroyed at the end of the use so I don't do that as well.

Is that a good way to use an external dll?
I've noticed that I have a memory leak and I thought that that might be the reason. Can that be the one?

Any advice will help!

Ofek Cohany
Apr 1 '07 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.