CODEWITHSUNDEEP
c#asp.net
afaf12
afaf12

Reputation: 5436

How to replace DLL files with .cs files?

I'm working on a sub-application for a large system.

There is a company X which has created the system. Sub-applications are created by numerous smaller companies, including the one I work for.

Our application is close to being finished but there is a new requirement that our application must not use DLL files and all the business logic should be contained in .cs files.

Why is there such a requirement? Company X believes it can solve the problem of having too many DLLs and dependency issues. With many sub-applications and many different companies creating them, problems arose with /bin directory and dependency issues.

Main problem is that many sub-applications are interlinked. Service Oriented Architecture is used.

I understand this is an architecture problem. And requirement also came way too late.

I'm a developer.

More specifically about my problem: It's simple when it comes to ascx.cs files, I can just switch from CodeBehind to CodeFile. No problem here.

Problem is with our libraries. Obviously, I can just copy all the corresponding .cs files on the server but how do I make the application load the classes from there instead of using DLL libraries?

I have never implemented an asp.net website without using DLLs, it is not clear to me what are my options.

I have been reading about: How to load a class from a .cs file

I hope I've explained my situation well enough.

Upvotes: 2

Views: 617

Answers (2)

Polyfun
Polyfun

Reputation: 9639

Offer to license your source code to them but at much higher price than the binaries. Source code has much more intrinsic value, because it is your intellectual property.

Also beware that company X can decompile your binaries into source code using e.g., ILSpy. How much do you trust them not to do this?

Upvotes: 2

Simon Whitehead
Simon Whitehead

Reputation: 65087

Company X no doubt has someone leading the developers who once had a dependency issue. They have now decided that any and all dependencies that are in the form of an actual assembly are bad (I think we've all had a manager like this at some point).

The fact is: this isn't possible. It is a stupid requirement that makes your life much, much more difficult.

You have two options that I can see.

1) Remove all of your (hopefully) nicely decoupled assemblies with their nice business logic out into your code behind files. This is tragic.. but an option.

2) Continue down your path of investigating compiling code from a source file. This sets you up for a HUGE amount of extra development time and.. honestly, you'll probably just end up giving up.

Save yourself some hassle and just offer them your full source code on USB.

Sorry if that sounds harsh. I do not envy you though.

Upvotes: 5

Related Questions