How to Deploy a Web Application in ASP.NET

October 26, 2006 at 12:00 pm (ASP.NET, Web Design)

To Deploy the Web Application You have created in ASP.NET follow the steps:-

1. Open the Web application project that you want to deploy. In this case,open the SampleVB project.

 2.Select File->New Project to open the New Project Dialog box.

3. From the Project Types pane, select Setup and Deployment Projects.From the Templates pane, select Web Setup Project.

4. Change the default name of the project. In this case, change it to “SampleVBDeploy.”

5. Click OK to complete the process. The project is added in the SolutionExplorer window. Also, a File System editor window appears to the left.The editor window has two panes. The left pane displays different items. The right pane displays the content of the itemselected in the left pane.

6. Select Web Application Folder in the left pane of the File System editor window
7.Then,from the File menu select Add -> Existing Website to open the Add Existing WebSite Dialog box.Choose the Web Application that you want to Deploy(In our case its SampleVB).The Web Application will be added in the Solution Explorer Window 8.Then, from the Action menu, select Add ® Project Output to open the Add Project Output Group dialog box.

9. Verify that SampleVB is selected in the Project drop-down list. Then,select Content Files from the list.

10. Click OK. The content files of the SampleVB project are added to the solution.

11. Select Web Application Folder in the File System editor and select Properties Window from the View menu to open the Properties window.

12. Set the VirtualDirectory property to a folder, <folder name>, that would be the virtual directory on the target computer where you want to install the application. By default, this property is set to SampleVBDeploy,which is the name of the Web Setup project that youadded. In this case, set the property to DeployedApplication.

Caution The <folder name> should be a new folder name and should not already exist on the target machine. Otherwise, the contents in the folder will be overwritten.
13. In the same Properties window of the Web Application Folder, set the DefaultDocument property to Default.aspx. This property is used to set the default Web Forms page for the application.

14. Build the solution by selecting Build Solution from the Build menu.

15. After the solution is built successfully, a SampleVBDeploy.msi file is created in the Debug directory of the Web Setup project. The default path is \documents and settings\<login name>\My Documents\VisualStudioProjects\SampleVB\SampleVBDeploy\Debug\
SampleVBDeploy.msi.

16. Copy the SampleVBDeploy.msi file to the Web server computer (c:\inetpub\wwwroot) where you want to deploy the application.

17. Double-click the SampleVBDeploy.msi file on the target computer to run the installer.

Note To run the installer, you must have the install permissions on the computer. And, to install to the Web server, you must have IIS permissions.

After the installation is complete, you can run your application on the target computer. Todo so, start Internet Explorer and enter http://<computer name or IP Address>/DeployedApplication in the address box.

Permalink 14 Comments

Trojan horse installs antivirus program

October 25, 2006 at 5:26 am (technews)

In addition to setting up a compromised computer to relay spam, one example of malicious software also installs Kaspersky Lab’s antivirus program to get rid of competing malicious software.

The culprit is a Trojan horse sometimes called “SpamThru,” according to a write-up by Joe Stewart, a researcher with SecureWorks. “SpamThru is a money-making operation, and the author takes great care to make sure that detection by the major vendors is avoided by frequently updating the code,” Stewart wrote last week.

When it first gets onto a PC, SpamThru connects to a control server and subsequently installs a pirated copy of Kaspersky AntiVirus, Stewart wrote. The system then starts a scan for malicious software, skipping files that it detects are part of its own installation, he wrote.

“SpamThru takes the game to a new level, actually using an antivirus engine against potential rivals,” Stewart wrote. “Any other malware found on the system is then set up to be deleted by Windows at the next reboot.”

Permalink 2 Comments

10,000 Fedora downloads in five hours

October 25, 2006 at 5:24 am (Linux)

If you’re curious what the appetite is for Fedora Core 6, Red Hat’s newest version of Linux for hobbyists, the company has an answer: 10,000 downloads in five hours.

Doing the math, that works out to one download every 1.8 seconds. And considering that the minimum size of Fedora Core 6 is 3.4GB, it’s no surprise Red Hat’s servers fell to their knees after the release Tuesday.

Although not all the downloads taxed the servers. The 10,000 statistic includes downloads through BitTorrent, a peer-to-peer file-sharing service that doesn’t tax central download servers as much as direct downloads.

Permalink Leave a Comment

Time’s Up: Internet Explorer 7 Coming This Month – oct 2006

October 25, 2006 at 4:53 am (IE, Web Design)

Microsoft has announced that the final version of the browser will be released before the end of this month—that’s less than two weeks away, people!

In the weeks following this initial release, Microsoft will deploy the browser to all Windows XP users via Automatic Updates. Although the installation of IE7 will not be forced as it was for Windows XP Service Pack 2 (users will be able to postpone or cancel the update if they so desire), a message will appear recommending that users proceed with the installation, which most of them undoubtedly will.

Chris Wilson, group Program Manager of the Internet Explorer Platform team at Microsoft, spoke at the Fundamentos Web 2006 conference and implored the developers there to test their sites with IE7 and fix any issues that appeared. There are a number of people on the IE7 team that have put their jobs on the line by implementing the standards compliance fixes and CSS features that we have been demanding for years, in some cases breaking compatibility with sites that were designed for the browser’s previous nonstandard behaviour.

As the dominant browser, Internet Explorer has the potential to effectively break the Web if the sites that everyday users rely upon do not work correctly in this new version. Despite this, Microsoft has taken an enormous leap of faith by sacrificing compatibility in the name of standards compliance. It’s up to us as developers to ensure that this leap of faith pays off, so that we can continue to see improvements to standards compliance in future releases of Internet Explorer.

You’re not on your own, here. Microsoft has produced an impressive array of tools and documentation to help developers migrate their sites to IE7

Permalink 4 Comments

How an Ugly, Mistake-Ridden Web Site Outperformed a ‘Better’ Site

October 25, 2006 at 4:47 am (Web Design)

We recently  redeveloped a web site for a client who sells a service at $5,000 a pop. Our redeveloped site replaced a site that he’d designed himself, which had been up for 6 months. It was an ugly, ugly site.

Yet, during its first couple of weeks online, the new site came nowhere near achieving the sales levels of the old, ugly site. Why? The answer reveals a fascinating insight into how some web sites work.

The old ugly site was mistake-ridden. It offered very little information. In no way did it present the client’s services in a positive way. But it still outperformed the new site by a long way, for one simple reason.

As there was no information on the web site, people phoned up my client. He’s great on the phone and made sales to 80% of these callers. He even made a $5,000 sale to a visitor who rang him to tell him about a typo on his web site!

My new (and better?) web site answered many of the prospects’ frequently asked questions, offered a 3-part email autoresponder course, and provided a lot of great information that was useful to visitors trying to make a buying decision.

In fact, there was so much great information that prospects didn’t need to call. So they didn’t. They made their buying decisions based on the information that was provided on the web site and the sales dropped like a stone!

The lesson to be learned here is that success is not about having the best-looking web site, the one with the most information, or the site with the highest traffic levels. It’s about what works.

I’d better go. I’m off to remove a whole lot of useful content and add a phone number to a homepage!

We represents a Group of Web Developers …

Permalink Leave a Comment