Keith Motte
|
| Posted: 03/01/2002, 5:14 PM |
|
When attempting to generate an application in C# I received the following error when trying to start application.
Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="Quotes.Global" %>
I've created a virtural directory. What going on? I have the released version of VS.Net and the released SDK.
|
|
|
 |
SN
|
| Posted: 03/01/2002, 10:04 PM |
|
1) The current verion of CodeCharge generates code compatiable with Beta2 version of .NET, but I have heard a big update to ASP.NET templates of CodeCharge is coming soon...
But you might try compiling the generated project for .NET Final .. in many cases it will compile correctly.
2) CodeCharge generates the application, but it does not auto-compile them. so you will have to compile the applications before you can run them. You can either run the "makeall.bat" batch file which is auto-generated by CodeCharge within the output directory to compile the code, or you can open the CodeCharge Generated Project in Visual Studio.NET (Necessary Project files are auto-created for you..) and then compile it.
Once you compile the code correctly, every thing should work correctly.
|
|
|
|
Sam
|
| Posted: 03/05/2002, 3:14 PM |
|
Does the current standard for ASP.net require that the application be compiled, or is it optional?
|
|
|
|
SN
|
| Posted: 03/05/2002, 9:51 PM |
|
Sam,
I did not get your exact question
But MS has recomended to use the Code Behind approach, where the UI and Code are stored in different files (*.aspx and *.cs).
CodeCharge *does* follow this standard and generate seperate files.
The only thing you need to do is manually compile the code generated by CodeCharge by running the 'makeall.bat' in the project folder... or you could use VS.NET to compile the project. This way you will be using compiled ASP.NET pages!!
A bit off-topic, there is not difference in the performance of an ASP.NET Web Application that follows in-line scripting or an compiled application. The only main benifit you gain by compiling the application is that your source code is secured...
|
|
|
|
Sam M
|
| Posted: 03/06/2002, 10:21 AM |
|
So are you saying that my .Net code would not be secured if I ran it as is out of cc, why is that?
|
|
|
|
SN
|
| Posted: 03/06/2002, 8:16 PM |
|
Sam M,
You did not get my point!
CodeCharge follows similar pattern of generating ASP.NET pages, like Visual Studio.NET. In Fact CodeCharge generates the code in Visual Studio.NET format, so *if needed* you can carry futher customization from within Visual Studio.NET.
Hence unless you compile your code (*.cs) the Web Application won't run !!
As far as security is concerned, CodeCharge produced code is totaly safe!
The reason I was saying as regards to security of compiled DLL is related to ASP.NET and not CodeCharge. Usually if you are a web developer, many customers require that you upload the site on the server before they pay you. Usually web developers are scared in such situation, since in other languages like ASP / PHP they have to give out the full source code to the client, and if the client later does not pay your hard work is gone  .
But using the compiled DLL approach you give your clients just the compiled DLL along with the *.aspx/*.ascx web pages. Since the code is compiled your source code remains safe even if the client wishes not to pay you!!
Is that clear??
|
|
|
|
Sam M
|
| Posted: 03/07/2002, 5:11 AM |
|
That makes more sense. Sorry about the misunderstanding.
|
|
|
|
|
