none
Should I include ASP.NET in my application? RRS feed

  • Question

  • Currently I have a WPF application which part of (certain windows) will be able to run in a browser using silverlight or standalone with the rest of the application. In this way, I hope that one code base will be required.

    My question concerns ASP.NET. Am I going to run into problems using this pure WPF/XAML solution as apposed to trying to combine my WPF/XAML application with some ASP.NET pages?

    I have no restrictions on customer installation of silverlight.
    I do not have any older ASP.NET code. Everything so far is using WPF 3.0/2.0.

    I briefly tried VS 2008 and WPF 3.5. The application ran but I did get some thrown exceptions related to data binding. Is the silverlight solution going to push me into VS 2008 right away?

    Any thoughts would be helpful.
    Tuesday, October 23, 2007 5:43 PM

Answers

  • I have not done development in it but my understanding both are deployed to IIS like SQL Server Reporting Services, which means integration in Asp.net is just an option it is not required.  The second link covers Microsoft configuration docs and the third link is a user adjustments for SilverLight.  Hope this helps.


    http://www.netfx3.com/

     

    http://msdn2.microsoft.com/en-us/library/c6e8c2cb-9ba2-4e75-a0d5-180ec9639433.aspx

     

    http://www.cjcraft.com/Blog/2007/05/08/HowToConfigureIIS50AndIIS60ToDeploySilverlightApplications.aspx

     

    Tuesday, October 23, 2007 8:18 PM
    Moderator
  •  

    My users are generally on an intraweb but will download data from the internet. A remote web site will be available to manage that data, but the local application will also have the same capability to manage its data. I was hoping to reuse as much code as possible for both purposes (local and server based).  ASP.NET is specifically developed for the web and now includes ajax support and a rath of additional capability. It looks like it will be easier to develop the web portion using ASP.NET with maybe some C# utilities that can be used both places. I think a pure WPF implementation will work for a web site but the development may be harder. It is just hard to live in so many code worlds at one time.

     

    Thanks,

     

    Friday, October 26, 2007 3:05 PM

All replies

  • I have not done development in it but my understanding both are deployed to IIS like SQL Server Reporting Services, which means integration in Asp.net is just an option it is not required.  The second link covers Microsoft configuration docs and the third link is a user adjustments for SilverLight.  Hope this helps.


    http://www.netfx3.com/

     

    http://msdn2.microsoft.com/en-us/library/c6e8c2cb-9ba2-4e75-a0d5-180ec9639433.aspx

     

    http://www.cjcraft.com/Blog/2007/05/08/HowToConfigureIIS50AndIIS60ToDeploySilverlightApplications.aspx

     

    Tuesday, October 23, 2007 8:18 PM
    Moderator
  • The second link above is useful for configuring my web server, but my question really was not about the web server. But about which development approach to take and the trade offs for each. The two approaches are described below.

    1. WPF and ASP.NET combined where the ASP.NET portion of the application runs in a web browser locally and via a web server.

    Or

    2. Pure WPF where a portion of the application will be executed via silverlight or a standalone application.

    I am investigating option two currently. I can generate XAML for a standalone application or for the web. The difference is the inclusion of silverlight support via javascript files. If I generate the XAML for the web do I have to generate it also for the standalone application or is the generated code completely compatible for both situations? I have almost answered this question but would still like to know what the pros/cons are for not using ASP.NET?

    A con might be that WPF does not support AJAX so I may see some performance problems. This is only an example con and may not even be true.

    Thanks,
    Jeff



    Wednesday, October 24, 2007 11:21 PM
  • PerfectStorm,

    I tried replying yesterday but I could not post, here is what you do if your users are outside users you cannot control you need a web application.  If your users are internal employees you can use WPF.  Hope this helps.

     

    Thursday, October 25, 2007 10:16 PM
    Moderator
  •  

    My users are generally on an intraweb but will download data from the internet. A remote web site will be available to manage that data, but the local application will also have the same capability to manage its data. I was hoping to reuse as much code as possible for both purposes (local and server based).  ASP.NET is specifically developed for the web and now includes ajax support and a rath of additional capability. It looks like it will be easier to develop the web portion using ASP.NET with maybe some C# utilities that can be used both places. I think a pure WPF implementation will work for a web site but the development may be harder. It is just hard to live in so many code worlds at one time.

     

    Thanks,

     

    Friday, October 26, 2007 3:05 PM