 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Visual Studio.NET / General / November 2003ASP.NET: What if I don't want a DLL?!
We are using VS.NET Pro 2003 to build web apps, but we would very much like to just use it to create the .aspx and .cs files and not have it force us to build a DLL. When we try to use the @Page Src= or @Control Src= (so it can reference an actual .cs file instead of the DLL), the web server has no problems, but when we try to load those files back into VS.NET to edit them, it yells and screams that src= is not allowed in VS.NET and it will have to be removed. Then it proceeds to remove the "Design" option from the aspx files that contain the offending Src=. Is there a way to tell VS.NET to chill out and allow us to design aspx pages, write .cs files etc etc without it freaking out over building a DLL and not allowing the more dynamic src= option? Anyone's suggestions are much appreciated. Clint Lord A DLL is required--- this is compiled code (MSIL). Your ASP.NET app will not run without it. Think about it... if you only have .cs files, it's NOT compiled --- ASP.NET is not an "interpretive" environment. m > We are using VS.NET Pro 2003 to build web apps, but we would very much > like to just use it to create the .aspx and .cs files and not have it force [quoted text clipped - 11 lines] > > Clint Lord Um... okay... I appreciate your response. Although it's untrue. You are correct that it's a compiled environment, but a DLL is not required, when you use src=, the .cs is compiled by the web server on the first request and then it's cached until the web server is restarted or a .cs file is changed... and even then only the file that was changed is recompiled on the next hit. So anybody that understands src= have any ideas how to make VS.NET not be so controlling? Clint Lord > A DLL is required--- this is compiled code (MSIL). Your ASP.NET app will > not run without it. Think about it... if you only have .cs files, it's NOT [quoted text clipped - 20 lines] > > > > Clint Lord VS.Net will only work with code behind AFAIK, so it will always complain if you use src=. MichaelR _is_ right, a .dll is always required - ASP.Net compiles a .cs file specified with src= to a .dll and caches it under C:\WINDOWS\Microsoft.NET\Framework\vn.nnnn\Temporary ASP.NET Files\ > Um... okay... I appreciate your response. Although it's untrue. You > are correct that it's a compiled environment, but a DLL is not required, [quoted text clipped - 37 lines] > > > > > > Clint Lord Ahem... Thank YOU Sheila... I'm often wrong about stuff so it's nice to be right for once. m > VS.Net will only work with code behind AFAIK, so it will always complain if > you use src=. [quoted text clipped - 50 lines] > > > > > > > > Clint Lord That's the impression I was getting (that VS.NET wouldn't let you use src=) - just wondered if anyone knew about a work around. As for the dll issue, I understand how the webserver compiles the dll and caches it... thus my explination about how the web server COMPILES the .cs... what I was saying is that it's not required to have a .DLL compiled by VS.NET or to deploy a web app. The web server takes care of the dll details. Thanks for the feedback. Clint Lord > VS.Net will only work with code behind AFAIK, so it will always complain if > you use src=. [quoted text clipped - 50 lines] > > > > > > > > Clint Lord The only workarounds I can think of would be either to edit and compile the project outside of VS.Net (e.g using the command line tools); or to put the source code in the .aspx file, as you would with asp (but you'd still have to have a code behind file and a .dll, even though there would be very little in them). > That's the impression I was getting (that VS.NET wouldn't let you use > src=) - just wondered if anyone knew about a work around. [quoted text clipped - 72 lines] > > > > > > > > > > Clint Lord I think you might want to evaluate WHY you want to do it the other way. Enlighten us. Perhaps someone here could talk you out of it. Personally I can't figure out why you would want to do it. A Web Server has enough work to do without compiling files also. JIT is bad enough. Wray > The only workarounds I can think of would be either to edit and compile the > project outside of VS.Net (e.g using the command line tools); or to put the [quoted text clipped - 86 lines] > > > > > > > > > > > > Clint Lord I work at a dot-com and we have THOUSANDS of ASPX pages. Our site changes too fluidly to make precompiled DLLs a workable solution for us. It would be OK if the original version of Visual Studio had exhibited this (ahem) "feature", but everything worked fine in the orginal VS with the Src= specified and using JIT. Now with VS.Net 2003 they've "added" this "feature" that makes any ASPX that is related to a JIT codebehind incompatible. This SUCKS. Clint, I feel your pain. Damm you Microsoft! John > We are using VS.NET Pro 2003 to build web apps, but we would very much > like to just use it to create the .aspx and .cs files and not have it force [quoted text clipped - 11 lines] > > Clint Lord Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.