views:

87

answers:

3

I didn't see an option to create a web site in the c++ area. Is there a way around this or am I just stuck with C# and VB.NET

+3  A: 

A bit of googling turned this up, not sure how applicable it still is: http://www.codeproject.com/KB/mcpp/helloworldmc.aspx

However, I'd question WHY you'd want to use C++.NET over C#, given that the languages are fairly similar at the basic level. Any perceived "speedups" would probably not be very noticable given that they both compile to the same IL, and as such are both subject to the JIT-compiler.

Daniel Bruce
Minor nitpick: it's not actually an interpreter. The JIT-*compiler* generates real native code on the fly.
Martinho Fernandes
You are correct. I was mixing the alternate CLR implementations (micro, in particular, as well as Mono's) with the "standard one," which DO interpret occasionally. My fault, fixed.
Daniel Bruce
+2  A: 

You can probably make your website work using C++/CLI. There is no tight coupling between a .NET page (aspx or ascx) and the language of implementation. You might even get the intellisense from within the aspx/ascx files but don't quote me on that.

So to set this up you would need to create a C++/CLI project and use managed C++ to extend Page, Control, etc classes, use HttpContext etc.

Another question is whether or not there is any point doing that. You would still be targeting .NET and calling to the same API. There won't be much performance benefit if at all and you will lose the IDE support for creating controls and you wouldn't be able to use WebForms from the designer.

Edit. If you haven't done ASP.NET before you will almost definitely be firing up a normal ASP.NET project and seeing how to implement something, which classes to extend etc. So it kind of defeats the idea of using another language.

Igor Zevaka
+1  A: 

You can, in theory, use any .NET language to build ASP.NET pages. F#, for example, is fully supported in VS 2010. Whether all languages are fully supported in the tools is another question -- particularly for a language like J# that has been deprecated beyond VS 2005 and doesn't support the full depth of features of the other languages (such as the ability to create new attributes).

At a minimum, you will need to do things like define an appropriate build provider to get things going.

RickNZ