My guess: You use managed code (Visual Basic or C#) for your ASP.Net.; likely you use code behind as part of your design pattern.
>From your reply (forgive me if I err ... for I guess) you are unaware of the openess and extensibility of the .Net architecture. NB. Microsoft designed .Net to allow additional .Net languages. Below, e.g. you will see "Dyalog APL for Microsoft .NET." ... so, if Iverson Software or someone else wishes, J.Net is possible and could be a very good symbiosis. FC _______________________________________________ .NET Framework applications are built on the services of the common language runtime and take advantage of the .NET Framework class library. http://msdn2.microsoft.com/en-us/library/ms229284(vs.80).aspx Develop Your Career with Microsoft .NET: Programming Languages http://www.microsoft.com/learning/training/roadmap/languages.mspx http://www.microsoft.com/learning/training/roadmap/framework.mspx#OTHER http://research.microsoft.com/fsharp/fsharp.aspx F# Combining the efficiency, scripting, strong typing and productivity of ML with the stability, libraries, cross-language working and tools of .NET. F# is a programming language that provides the much sought-after combination of type safety, performance and scripting, with all the advantages of running on a high-quality, well-supported modern runtime system Designing Distributed Applications with Visual Studio .NET Programming Languages http://msdn2.microsoft.com/en-us/library/aa292164.aspx The .NET Platform programming languages — including Visual Basic .NET, Visual C#, Managed Extensions for C++, and many other programming languages from various vendors — use .NET Framework services and features through a common set of unified classes. The .NET unified classes provide a consistent method of accessing the platform's functionality. If you learn to use the class library, you will find that all tasks follow the same uniform architecture. You no longer need to learn and master different API architectures to write your applications. Alternative Languages Microsoft partners with many companies to bring their languages to the .NET Platform. In addition to the languages provided by Microsoft, there are many alternative languages that target the .NET Platform, including: COBOL for Microsoft .NET. Perl for Microsoft .NET. Eiffel for Microsoft .NET. Python for Microsoft .NET. Pascal for Microsoft .NET. Mercury for Microsoft .NET. Mondrian for Microsoft .NET. Oberon for Microsoft .NET. Salford FTN95 (Fortran) for Microsoft .NET. SmallTalk for Microsoft .NET. Standard ML for Microsoft .NET. Dyalog APL for Microsoft .NET. For more information, contact your language vendor. On Sun, Apr 20, 2008 at 6:29 PM, Raul Miller <[EMAIL PROTECTED]> wrote: > On Sun, Apr 20, 2008 at 4:38 PM, frank clooter <[EMAIL PROTECTED]> wrote: > > The Microsoft .Net 3.5 Framework is supposed to work with any language. > > With ASP.Net and the Framework (it's CLASS library), it's really easy to > > make even AJAX web pages. > > > > Is J ready for .Net? If not, when? > > I use .Net. I use ASP.Net. I use AJAX. I use AJAX with ASP.Net. > > However, I do not have a clue what you are talking about. > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
