I am use web matrix for my asp.net project because visual studio is too expensive for me. But thing is it is only 1.3 MB is size and visual studio .Net is more then 2 GB in size! If it is going to do same thing than what is the main difference between Web Matrix and visual studio .Net??I have used it, not as much as I would like.
If you are learning then this is great... it does all the basics and more. You have to walk before you can run Sir.
The only thing that I have come 'acropper' with is... code behind files. I might be wrong but not sure if Matirx does code behind.
Try it... it is free... what have you got to lose?i didn't like it too much, but that's because i have Dreamweaver instead...
as for code behind, you don't really need VS.NET to utilize it... here is an article from 4guysfromrolla showing how to do it without VS.NET:
<!-- m --><a class="postlink" href="http://www.asp101.com/articles/john/codebehindnovs/default.asp">http://www.asp101.com/articles/john/cod ... efault.asp</a><!-- m -->
and the MSDN article:
<!-- m --><a class="postlink" href="http://msdn.microsoft.com/msdnmag/issues/01/08/cutting/default.aspxFrom">http://msdn.microsoft.com/msdnmag/issue ... t.aspxFrom</a><!-- m --> the article it just looks like they pre-compiled the code-behinds then pointed the page directive to it.No, you don't have to precompile.. that was one of the options they provided.. that's if you use the Code Behind attribute in the page directive to point to the actual class name
however if you read it, it also shows how to point to the source file using SRC= <!-- m --><a class="postlink" href="http://www.htmlforums.com/archive/index.php/instead..">http://www.htmlforums.com/archive/index.php/instead..</a><!-- m -->. and ASP.NET will autocompile it for you...
From the article:
So to sum everything up... all it really takes to do code-behind is one little inherits attribute in your page declaration line specifying the name of the class you want to inherit. If you're willing to precompile your classes into .dll files, that's where it stops. If you're lazy like me or like the "edit and run" simplicity that classic ASP gave you, add a src attribute pointed at your code-behind file and ASP.NET will compile it for you. That's really all there is to it.
i've tested it and it works great. only thing you have to do is make sure you declare all your controls explicitly, and import namespaces (VS.NET does that automatically with its projects too)
If you are learning then this is great... it does all the basics and more. You have to walk before you can run Sir.
The only thing that I have come 'acropper' with is... code behind files. I might be wrong but not sure if Matirx does code behind.
Try it... it is free... what have you got to lose?i didn't like it too much, but that's because i have Dreamweaver instead...
as for code behind, you don't really need VS.NET to utilize it... here is an article from 4guysfromrolla showing how to do it without VS.NET:
<!-- m --><a class="postlink" href="http://www.asp101.com/articles/john/codebehindnovs/default.asp">http://www.asp101.com/articles/john/cod ... efault.asp</a><!-- m -->
and the MSDN article:
<!-- m --><a class="postlink" href="http://msdn.microsoft.com/msdnmag/issues/01/08/cutting/default.aspxFrom">http://msdn.microsoft.com/msdnmag/issue ... t.aspxFrom</a><!-- m --> the article it just looks like they pre-compiled the code-behinds then pointed the page directive to it.No, you don't have to precompile.. that was one of the options they provided.. that's if you use the Code Behind attribute in the page directive to point to the actual class name
however if you read it, it also shows how to point to the source file using SRC= <!-- m --><a class="postlink" href="http://www.htmlforums.com/archive/index.php/instead..">http://www.htmlforums.com/archive/index.php/instead..</a><!-- m -->. and ASP.NET will autocompile it for you...
From the article:
So to sum everything up... all it really takes to do code-behind is one little inherits attribute in your page declaration line specifying the name of the class you want to inherit. If you're willing to precompile your classes into .dll files, that's where it stops. If you're lazy like me or like the "edit and run" simplicity that classic ASP gave you, add a src attribute pointed at your code-behind file and ASP.NET will compile it for you. That's really all there is to it.
i've tested it and it works great. only thing you have to do is make sure you declare all your controls explicitly, and import namespaces (VS.NET does that automatically with its projects too)