Avatar of David L. Hansen
David L. Hansen
Flag for United States of America asked on

Converting DLL to be compatible with ASP

I have a DLL, that had a number of WinForm objects in it, that I've prepped for use in ASP.  To do this I removed all instances of WinForm objects, or calls, from the library and recompiled. I've given the new library to our web-developer and he says it doesn't work. I can confirm that the library has no more lingering WinForm code or objects in it and that it compiles without issue. It's in C# to match with the ASP project and I've tried compiled with Framework 3.5 and also 4.0 (neither helped). I wonder if the framework is the issue actually. Our ASP project is using ASP.Core.

Any ideas?
ASP.NET ProgrammingC#

Avatar of undefined
Last Comment
David L. Hansen

8/22/2022 - Mon
David Johnson, CD

asp is not compatible with asp.net
It really is time to upgrade your legacy web application to use asp.net, It's only been 15 years since .net was introduced
SOLUTION
Ryan Chong

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
kaufmed

What do you mean by "it doesn't work"? What is the error message?
David L. Hansen

ASKER
David, I appreciate your chiming in but I think you've got the situation wrong. I'll try and elaborate. There is no legacy web application. We've never done ASP until very very recently. As far as the DLL in question, it's gone through many iterations and changes (and it's currently built on Framework 4.5).  The issue is that it's primarily been consumed by WinForm applications and now needs to be leveraged by an ASP application.  Frankly, It just hasn't ever been used in a web-space because...well, this is government work...you understand.

Anyway, our developer says he gets a message when attempting an to import the library, which essentially says: "Because of the framework, you have to import this DLL as a nuget package" (his words..not mine).
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
kaufmed

You keep saying "ASP", but you mention "ASP.Core". So is this classic ASP (i.e. "ASP") or is this ASP.NET (including ASP.NET Core)?
ASKER CERTIFIED SOLUTION
David Johnson, CD

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
David L. Hansen

ASKER
Kaufmed, it definitely is .Net Core.

David, I believe that's just what our developer tried. He's placed the DLL file on the dev-machine and tried to import it through VS's Solution Explorer.
SOLUTION
David L. Hansen

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
David L. Hansen

ASKER
Sorry for not closing this earlier (I thought I had already done so...my bad).
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.