152 reputation
16
bio website
location
age
visits member for 3 years, 2 months
seen Mar 20 '13 at 22:44

Aug
29
awarded  Notable Question
Mar
16
awarded  Popular Question
Nov
13
awarded  Supporter
Nov
13
accepted How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
Nov
13
accepted How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
Nov
13
comment How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
Hi Chris. Thanks for replying. Yeah, you're probably correct about me not using correct terms. Since I'm no networking/security expert (I'm a developer and, up until now, we've only had to worry about installing our Windows forms apps on a single server with simple Windows authentication), I'm just trying to understand some things so I can speak somewhat intelligently to IT people, and figure out if we have to change our application in any way. What you've said (in addition to the other replies) makes sense. I'll investigate further. Thanks again.
Nov
13
comment How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
... Assuming the firewall stuff between the two servers is correct, do I just need to change my DB connection string to find the SQL Server? Or? Thanks! It appears that this post was migrated from stackoverflow.com, so now there's two on serverfault. Sorry.
Nov
13
comment How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
... I was having trouble with this scenario. From a client browser (mobile Safari since this app is intended for mobile devices), I type in the URL to the IIS server (e.g., servername/appname) and get the HTML/CSS/JS downloaded to the browser. Inside one of my JS files, I make an AJAX call to the Web API (e.g., servername/appname/api/getitems). This all work locally when IIS and SQL Server are all on the same machine. Is there something else I need to do different to work in production where IIS and SQL Server are on two separate servers? ...
Nov
13
comment How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
Hello Chris. Thanks for replying. You are correct; that is, the application as it stands right now is a SPA in which the client gets all the HTML/CSS/JS on the initial request and after that only REST calls are made to the Web API. The Web API controllers on the server issue SQL queries directly to the database and return JSON data (in the case of GETs, for example). To clarify, you're suggesting putting everything (the HTML, CSS, JS, Web API assemblies, etc.) all on the IIS server in the DMZ and then send only queries to the SQL Server through port 1433? ...
Nov
13
comment How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
... Assuming the firewall stuff between the two servers is correct, do I just need to change my DB connection string to find the SQL Server? Or? Thanks again!
Nov
13
comment How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
... I was having trouble with this scenario. From a client browser (mobile Safari since this app is intended for mobile devices), I type in the URL to the IIS server (e.g., servername/appname) and get the HTML/CSS/JS downloaded to the browser. Inside one of my JS files, I make an AJAX call to the Web API (e.g., servername/appname/api/getitems). This all work locally when IIS and SQL Server are all on the same machine. Is there something else I need to do different to work in production where IIS and SQL Server are on two separate servers? ...
Nov
13
comment How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
Hello Brent. Thanks for replying. You are correct in your assumptions; that is, the application as it stands right now is a SPA in which the client gets all the HTML/CSS/JS on the initial request and after that only REST calls are made to the Web API. The Web API controllers on the server issue SQL queries directly to the database and return JSON data (in the case of GETs, for example). To clarify, you're suggesting putting everything (the HTML, CSS, JS, Web API assemblies, etc.) all on the IIS server in the DMZ and then send only queries to the SQL Server through port 1433? ...
Nov
13
comment How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
Hi Tim. Thanks for replying. Yeah, you're probably correct about the question being broadly scoped. I had a difficult time writing it, trying to convey all the pieces and information without writing a book. Since I'm no networking/security expert (I'm a developer and, up until now, we've only had to worry about installing our Windows forms apps on a single server with simple Windows authentication), I'm just trying to understand some things so I can speak somewhat intelligently to IT people, and figure out if we have to change our application in any way. Thanks again.
Nov
12
asked How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
Nov
12
asked How to Deploy an ASP.NET Web API- and Browser-based Application to a Production Environment
Nov
1
awarded  Scholar
Nov
1
accepted Cannot Add Windows Server 2012 as Member Server to Existing Domain
Nov
1
accepted Help/Questions About New Team Foundation Server 2010 Installation
Oct
12
asked Cannot Add Windows Server 2012 as Member Server to Existing Domain
Nov
24
awarded  Teacher