Package/Publish in C#.NET

Printing Code 3 of 9 in C#.NET Package/Publish

For Web applications, there is an answer too and one that will fix my poor application in the previous section, Copy Web sites with Copy Web Package and Publish is designed to assist with more sophisticated deployments usually found with Web Application projects To get to the package and deployment options, double-click on the Properties folder in the project, and then click the Package/Publish tab on the left-hand side of the designer surface This panel, shown in Figure 5-9, has everything you need to solve most mid-range deployment problems Starting at the top you can isolate 64-bit operating systems with the Platform drop-down list This is good when you are developing in 32 bit but know your server is 64 Right below that is a link to the Help files, in case you don t have this chapter handy

In the Items to Deploy section, you can solve the big problem that I mention earlier There you can tell the deployment to deploy only markup and compiled files, if that is what you need to do There are options to exclude debug symbols, too remember, they don t run if they aren t there, and it all goes a little faster You can always add them if you need them You now can use MsDeploy with Visual Studio MsDeploy is a new feature of IIS that assists with the deployment of really complex Web applications Search for it on TechNet for more information It takes a Zip file, which you can configure in the MsDeploy Package Settings section

1: Getting Acquainted with Web Services 719 2: Building Web Services with ASMX 731 3: Building Web Services with WCF 745 4: Building Web Services with ReST 759

Exploring the basic principles of service-oriented apps Building service-oriented apps Making XML Web services available

Web service is just the provision of functionality over the Internet using an open interface A Web page provides functionality that you can see; a Web service provides the underlying data, in a format that you can use in another application Web services are straightforward at least until the software manufacturers start messing with them Web services are standards driven, just as HTML is, and the World Wide Web Consortium (W3C) owns their documentation Web services have been a hot topic for the past decade, but only in the past five years or so (in step with the ubiquitous nature of the Internet) have they become a viable option for the delivery of hard-to-find software functionality A few different Web services formats exist in the NET world, and they solve two basic problems: Making part of your application available past the physical boundary of the application Making a distributed middle to your application so that you can scale paragraphs if your site suddenly has a lot of traffic

Web services provide a way to extend methods past the normal boundary of a software system You usually write the something like the following chunk of code in order to start building a problem:

public bool AddStuff(String stuff) { //Add it here return true; }

and then you call it like this:

bool DidItWork = AddStuff( This is the new Stuff );

Using Web services, however, you call the method this way:

POST /Service1asmx HTTP/11 Host: localhost Content-Type: application/soap+xml; charset=utf-8 Content-Length: length < xml version= 10 encoding= utf-8 > <soap12:Envelope xmlns:xsi= http://wwww3org/2001/XMLSchemainstance xmlns:xsd= http://wwww3org/2001/XMLSchema xmlns:soap12= http://wwww3org/2003/05/soap-envelope > <soap12:Body> <AddStuff xmlns= http://tempuriorg/ > <stuff>string</stuff> </AddStuff> </soap12:Body> </soap12:Envelope>

and then see a response like this one:

HTTP/11 200 OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length < xml version= 10 encoding= utf-8 > <soap12:Envelope xmlns:xsi= http://wwww3org/2001/XMLSchemainstance xmlns:xsd= http://wwww3org/2001/XMLSchema xmlns:soap12= http://wwww3org/2003/05/soap-envelope > <soap12:Body> <AddStuffResponse xmlns= http://tempuriorg/ > <AddStuffResult>boolean</AddStuffResult> </AddStuffResponse> </soap12:Body> </soap12:Envelope>

Whoa! Hey, why would anyone want to build a function that way I m glad you asked In the later section Building Service-Oriented Applications, I answer your questions For now, I describe some concepts that make building web services easier to handle Web services can be defined by three basic principles: