I like the idea of having these run in IIS but that would require a dependency on IIS. I believe the reason the WCF applications are hosted in command windows now is that allows them to be hosted on any machine (including a machine that doesn't have IIS or Visual Studio) installed. Self hosting in a command window is the safest and easiest way to host a WCF service since WCF itself doesn't have/force a hosting model. This allows for easier setup and for having the front end, services, and database all run on separate machines. I could move the services to be hosted in IIS so they would always be available but it would make the build/deploy process a little more difficult and require instructions on how to set up the virtual directories for the services. I am also not sure if it would simplify the instructions that much as we would have to modify the setup instructions to open multiple instances of Visual Studio. I am lazy so I decided to create a batch file using the start command to create the two command windows and run the executables so I only have to type one command :) If everyone feels that the command windows are a big problem I can change the code but I don't think that should be a high priority task.
Scott Golightly -----Original Message----- From: Drew Baird (Volt) [mailto:[email protected]] Sent: Tuesday, April 14, 2009 11:29 AM To: [email protected] Subject: RE: Running .NET Business/Order Services from VS versus Command Line Another thought (and my druthers) would be to convert them to real services not just console apps. -----Original Message----- From: Art Rybakov [mailto:[email protected]] Sent: Tuesday, April 14, 2009 7:55 AM To: [email protected] Subject: RE: Running .NET Business/Order Services from VS versus Command Line The main advantage would be not having 2 more instances of open Visual Studio development environment in the memory draining the resources. I assume that for a developer who is knowledgeable enough to run services from a Visual Studio it is not a big effort to run them from a command prompt. This is just my opinion based on personal preferences and I know people who would not mind have multiple instances of VS though. But if we are talking about guide line then advising for a command prompt is more in line with the best practices. Regards, Art Rybakov -----Original Message----- From: Ben Dewey [mailto:[email protected]] Sent: Tuesday, April 14, 2009 10:37 AM To: '[email protected]' Subject: Running .NET Business/Order Services from VS versus Command Line Guys, I was going over the install documentation for the .NET ST and noticed that we might be able to simplify them if we just have people Run directly from VS. Here is what I was thinking (please pardon my shorthand): At the moment the doc says (https://svn.apache.org/repos/asf/incubator/stonehenge/trunk/stocktrader/dot net/ReadMe.mht): 1. Build the Project a. Build OrderProc Service b. Build Business Service c. Build Trade 2. Run the project a. Open cmd (as admin) and run OrderProc Service b. Open cmd (as admin) and run Business Service c. Open http://localhost/trade Instead we could 1. Open OrderProc Service, hit F5, don't close 2. Open Business Service, hit F5, don't close 3. Open http://localhost/trade Thoughts? Are there any advantages to running from cmd instead of running from Visual Studio? Ben Dewey Senior Software Developer twentysix NEW YORK 62 West 45th Street, 5FL New York, NY 10036 T (212) 840 0008 F (212) 840 9490 www.26NY.com<http://www.26NY.com> Heard about Microsoft SQL Server 2008 and want to know more? Register for Andrew Brust's Webcast OLAP Development Using SQL Server 2008<https://www.clicktoattend.com/invitation.aspx?code=133837> Check our Web site<http://26ny.com/content/4.2_events.html> regularly for other topics and dates Microsoft Gold Certified Partner
