Until now, there's been only few posts regarding .Net in MX. Possible explanations:
1. .Net developers think that MX isn't good enough.
2. .Net developers went to other forums.
3. Macromedia's fans don't like .Net.

I was just wandering what do you think about MX and .Net.

Viktor Farcic
www.farcic.com
TalkZone Manager

.net? mmm well someone tell me all issues have been sorted out, cuz the last time i installed it my IIS server would kill the box CPU usage would shoot up to 100% and stay dere *shrug* so uninstalled havnt installed it again since then .. ane1 tested it out post here <img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle> pls...

I just built my first dwmx asp.net application. I will be posting tutorial and the resulting code soon.

I'm just waiting until I have enough time to make the switch to .net development. From my understanding there is quite a change from ASP 3.0 and that VB.net is more closely related to Visual Basic than ASP. So for someone like myself that has never really used VB or Visual C# I think there is quite a lot to catch up on before I would be as comfortable and proficient with ASP.net as I am with ASP/VBScript.

In addition, there are still relatively few hosts that support ASP.net when compared to ASP 3.0, I'm hoping that by the time I have got to grips with the new methodilogy there will be more choice. I have noticed some hosts charging extra for ASP.net hosting, which seems a bit cheeky considering the framework is free to download from Microsoft.

Regards

Owen.

Multiple Parameter UD4 / Access 2000 Database Search Tutorial:
www.tdsf.co.uk/tdsfdemo

I just got done a while ago with my first site conversion from Dreamweaver 4-generated ASP to MX-generated .Net ASPX. I think you hit the hammer on the head with all three of your explanations, actually.

MX is simply not the tool you want to use for ground-up .Net work yet: the lack of a code-behind implementation takes a lot of the .Net advantage away. Our company is rewriting sites for the express purpose of the code-behind features, and since MX doesn't do it, then you might as well use VS.Net.

As far as #2, I don't think this forum is the place for strong .Net help.

And for #3, I'd have to say that based on my first site conversion, I'm not itching to go through that again. Since I don't build ground-up sites every month, it'll probably be a while before I use MX to do a .Net site.

What's your damage, Heather?

What are the Advantages and Disadvantages of Using .net for MX? In a nutshell.

Viktor,

Which language are you using? VB.net or C# for ASP.NET

VB.Net

It's a matter of choice. There are no real advantages in any of .Net languages.

<BLOCKQUOTE id=quote><font size=1 face="Verdana, Arial, Helvetica" id=quote>quote:<hr height=1 noshade id=quote>
Viktor,

Which language are you using? VB.net or C# for ASP.NET


<hr height=1 noshade id=quote></BLOCKQUOTE id=quote></font id=quote><font face="Verdana, Arial, Helvetica" size=2 id=quote>

Viktor Farcic
www.farcic.com
TalkZone Manager

Edited by - vfarcic on 12 Jul 2002 09:28:28