locked
2-tier deployment on local network RRS feed

  • Question

  • I need help with a 2-tier deployment. The client computers are on a win 2008 server network. The lightwitch data is housed in a SQL server 2005 database on the server. I have no trouble in connecting to the database from within VS 2012 lightswitch on a client computer. When it comes to deploying I having all sorts of problems. Can anybody point me the right direction. Thanks.

    TimGLewis

    Thursday, May 2, 2013 3:13 AM

Answers

  • Is an internal web server an option?

    After trying out the all of the options, I found much better performance doing the desktop from a web-server.

    I'm not sure what the best practice for this is, but you could at least 'try' this by pulishing to your computer, and then loading the app from the client.

    In my limited experience, it is just better to have the Web server middle tier because it leaves the client computer to be very responsive.  Then the client computer doesn't have to be as powerful.  Also, it just seemed in the 2 tier setup to bog down because of the local SQL server instance.

    So, what I did is have the Hardware Guys throw together a Windows Server (it was a 2008) that was set for Web already (hosted on our HyperV).  On top of that I installed SQL Server Express, including the Reporting Services, as the default instance so I have an easy database for the intristic database separate from the application data (App data exists on SQL Server 2005 at various locations throughout the company).  On top of that I installed the rest of the LightSwitch pre-requisites.  Then I just publish from to there.

    Doing it that way makes it so I point users to the website for installation.  Also, if you choose to host part (in my case, MOST) of my app as a browser based, it is all set!

    Anyway, I don't know the answer to your exact question, hopefully the long-time participants will weigh in and either verify what I'm saying, correct me, clarify what I've said, or answer your question directly.

    Good luck!


    Would someone please turn on the LIGHT?

    Thursday, May 2, 2013 3:20 PM
  • Hi Tim,

    Joe's advice is good advice. If you can do it, deploy the middle-tier to a web server and then have clients hit it to install the desktop client. This means that you only need ONE login to the database and you can share connections, which makes you app a lot more scalable.

    I suspect the reason why some computers work and some don't is that some computers have access to the database on the network and some don't. If you can centralize this with a web server it is much easier to manage as the number of clients grow.

    HTH,

    -Beth


    Senior Program Manager, Visual Studio Community http://www.bethmassi.com http://msdn.com/lightswitch http://dev.office.com

    Friday, May 17, 2013 11:43 PM

All replies

  • Is an internal web server an option?

    After trying out the all of the options, I found much better performance doing the desktop from a web-server.

    I'm not sure what the best practice for this is, but you could at least 'try' this by pulishing to your computer, and then loading the app from the client.

    In my limited experience, it is just better to have the Web server middle tier because it leaves the client computer to be very responsive.  Then the client computer doesn't have to be as powerful.  Also, it just seemed in the 2 tier setup to bog down because of the local SQL server instance.

    So, what I did is have the Hardware Guys throw together a Windows Server (it was a 2008) that was set for Web already (hosted on our HyperV).  On top of that I installed SQL Server Express, including the Reporting Services, as the default instance so I have an easy database for the intristic database separate from the application data (App data exists on SQL Server 2005 at various locations throughout the company).  On top of that I installed the rest of the LightSwitch pre-requisites.  Then I just publish from to there.

    Doing it that way makes it so I point users to the website for installation.  Also, if you choose to host part (in my case, MOST) of my app as a browser based, it is all set!

    Anyway, I don't know the answer to your exact question, hopefully the long-time participants will weigh in and either verify what I'm saying, correct me, clarify what I've said, or answer your question directly.

    Good luck!


    Would someone please turn on the LIGHT?

    Thursday, May 2, 2013 3:20 PM
  • Hi Tim,

    Joe's advice is good advice. If you can do it, deploy the middle-tier to a web server and then have clients hit it to install the desktop client. This means that you only need ONE login to the database and you can share connections, which makes you app a lot more scalable.

    I suspect the reason why some computers work and some don't is that some computers have access to the database on the network and some don't. If you can centralize this with a web server it is much easier to manage as the number of clients grow.

    HTH,

    -Beth


    Senior Program Manager, Visual Studio Community http://www.bethmassi.com http://msdn.com/lightswitch http://dev.office.com

    Friday, May 17, 2013 11:43 PM