views:

331

answers:

4
+3  A: 

The Delphi.Net functionality was removed after Delphi 2007, so I am not sure why you do not see the project type. But as Delphi.Net is a pretty dead technology it would probably make sense to look for an alternative for .Net development like Delphi Prism or C#.

Lemmy
Actually it's removed after Delphi 2007, Delphi 2007 was support .Net v2 while Delphi 2006 supports only .Net 1.1.
Mohammed Nasman
so, what you are saying Lemmy is that we should use Prism then, is that it?
balexandre
Mohammed: Oh sorry I didn't know Delphi 2007 still had it. balexandre: I'd just suggest not to use Delphi.Net because that is a dead-end. If you want to do asmx, pick Delphi Prims, C#, VB.Net or any other .Net language you feel comfortable with.
Lemmy
the idea was to use pascal but outputs an ASP.NET Web Service and not that 'stupid' ISAPI DLL :)so we can reuse plenty of code already written in pascal. We really do not want to create new code (as I'm a C#/VB developer it would be extremely painful to rewrite everything again, tested, etc ...)
balexandre
well in that case Delphi Prism sounds like the logical way to go for you. But I personally have never used it so I don't know how stable and Delphi-compatible it is. You'll surely have issues with several things like string indices (0-based in .NET, 1-based in Delphi, Garbage Collection and missing framework classes), but someone with more experience with Delphi Prism can surely better explain how bad those pain points are in real life. Delphi.Net surely has fewer of those painpoints, but its compatibility to class Delphi really constrained it too much. Thats why it ultimately failed.
Lemmy
Great i wrote "surely" three times in a single post. Bad bad Lemmy...
Lemmy
Lemmy: you should consider correcting your answer (the goal of SO is to have correct answers).
Argalatyr
so, the bottom line is... There is no Good support for pascal code in order to build ASMX Services, we should do everything from scratch again using ... PRISM? so why prism? and not just plain old Visual Studio ASP.NET Web Service project in C#/VB ?
balexandre
I agree with balexandre. I don't see a strong advantage in Prism. And if you go with VS, you still don't have to like it. As long as it is only easier :-)
Marco van de Voort
A: 

Actually, since Delphi 2007, the functionality has been split into three different product, plus a fourth studio product. There's Delphi for WIN32 which includes C++ and Delphi for .NET which includes C# and ASP.NET. And then there's the Developers Studio which combines these development systems into one product. There are also products called Turbo Delphi, Turbo C++, Turbo C# and Turbo Delphi for .NET.

To be honest, Borland/Codegear/Embarcadero is trying to find the most popular combinations of these products making it very unclear for developers to choose the right version. Now we have Delphi Prism for .NET which integrates in Visual Studio, plus Delphi and Delphi for .NET or whatever. Anyway, I stopped upgrading Delphi since I bought Developer Studio 2007 simply because they're making a big mess of their marketing strategy.

Plus, they're becoming too expensive. For .NET development, Visual Studio will provide plenty of options already, especially when designing web applications. I will upgrade once the price becomes reasonable again and their marketing strategy becomes more normalized. I fear it will be a cold day in Hell when that happens.

You're probably using just the WIN32 version, not the Studio version which would combine both. Or you just installed the WIN32 and not the .NET part! Or, with Delphi 2007, you just start the WIN32 identity, not the whole Studio identity. (Delphi will install multiple icons, one for Delphi/WIN32, one for C++, one for C#/.NET and one for the complete studio.)


Just adding that I myself use the RAD Developer Studio 2007 and it does contain the ASP.NET Web Services. Just make sure you've included them during installation!

Workshop Alex
So, in order to use pascal code that, today, outputs an ISAPI DLL Service, what will you recomend in order to reuse the same code but to output an ASMX Web Service? So I can integrate in our ASP.NET Web Site projects that we are lunching, part of a new line of products? My problem is that I want to reuse all the existing code from our Delphi developer, and slpit his work in 2, Core feature in a WebService(s) and Presentation (Delphi for Windows and ASP.NET for Web). Thank you for the tip though.
balexandre
A: 
balexandre
I strongly suggest you create a new _project_, not a new web site. The Web Site Project model is too simpleminded for a web service.
John Saunders
A: 

Hi, this topic holds a lot of useful information for me. I haven't found the Delphi .NET in 2010 neither. My question is that can I install a simple VCL component package (dpk) under Prism and can I use it in a .NET project?

Thanks for the help guys.

Yany