11 November, 2011

Troubleshooting WebSite publishing in Windows 7

Windows logoImage via Wikipedia11-Nov-2011

This is how I found out about the 'BIG' difference between 'COPYING' and 'COMPILING' when publishing a web site, in Windows 7.

  • Follow deployment tutorial from MSDN (compiled web site, published locally)
  • Error: ASP.NET 4.0 application error: Unrecognized attribute 'targetFramework'...
  • Change IIS DefaultAppPool .NET Framework Version to "4.xxx".
  • Error: HTTP Error 500.21 - Internal Server Error
  •  
  • Run "%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i". This is to correct installation of ASP.NET
  • Error: none; website is displayed correctly, and working.
NOTE: \Framework\vN.xxx\ -> this is according to the version that is installed in your computer.
Check from the following folder: C:\Windows\Microsoft.NET\Framework\

I hope that this will be of help to many developers like me who struggles with using the latest technologies, but get stuck somewhere in the middle, one way or another...

Till then!

Enhanced by Zemanta

Publishing a Web Site in Windows 7

The Microsoft sign at the entrance of the Germ...Image via Wikipedia11-Nov-2011

I think I have finally figured out how to publish a web site in Windows 7. I mean, I managed from my limited knowledge years ago to create a very simple web site that performs just a number of functions, put it in one of the desktop PCs, and since it is working as expected, forgot all about it, how I created it from scratch, how I put the things altogether, and finally, how to make it run.

Now, with the series of migration being done for at least 4 PCs from Windows XP to Windows 7, what is keeping me back from migrating all to Winows 7 is the simple web apps that I can't figure out anymore how I put up.

I have already spent many days (and weeks) testing, recreating, compiling, publishing, copying, running - all to no avail. The web apps run fine when run in debug mode, but once deployed, one error after another comes up. And even with the help that I get from the web, the errors don't go away. I'm stuck.

Today, I may just be fortunate to have some time to read again and again the tutorial on Walkthrough: Deploying a Web Site Project by Using the Publish Web Site Tool, which is from MSDN. Now, this is by way of publishing a web site. The one that I have always been testing and testing is publishing by Copy method.

Then, in one of the links of the related topics, I chanced upon a very simple revelation: publishing a web site by copy method means you need to have FrontPage Server Extensions. That would have been alright, since I immediately found it by way of a quick Google search. Then, boom! It is not free...

Anyway, I have already made the other method working for me, so I will nwo stick to the new method of web site publishing: Compiled Site.

I guess, that is due to some security issues, that while it is allowed (so easily) in Windows XP, being described a more secure OS, Windows 7 has to be right and rigid. And I got hit with that mantra. But now I know.

I'm now preparing to migrate my simple web site for publication in a PC running Windows 7. And all my codes can now safely run in that OS.

Till then!

Enhanced by Zemanta

03 November, 2011

File Manager other than Windows 7's Windows Explorer

Image representing Windows as depicted in Crun...Image via CrunchBase I thought I have posted an article about file manager in Windows 7, but as I checked today, there is none!

Well, what prompted this search for an alternative file manager is the poor performance of the same application that is provided by Windows 7. I mean, the Windows Explorer is working fine in Windows XP, but when it comes to Windows 7 (I can’t remember how this fared in Windows Vista), the thing just sucks!

When does it not perform well? The performance is already bad even with a single-instance copy session. The worst comes when while that single-instance copy session is still ongoing, and you initiate another copy (or delete) session, then the duration or countdown to file transfer/delete completion skyrockets from minutes to hours! If you really want to ‘play with it’, add more file copy/move/delete session, and the numbers don’t move anymore.

I wanted to stop this there and then, because I cannot stop thinking why it behaves this way, the Windows 7 file manager. I searched the web, and I found several solutions, and of course, not all are acceptable, and while many work, not many are quite promising.

FastCopy – I couldn’t say anything about this application, because I can’t figure out much of its menu or instructions. I’m not being racist or whatever, but it is like flying a jet plane with all the button and switches written in another language. One wrong button and your plane will just crash!

NiceCopier – This I am using at home. I find that it is most advantageous when used for localized file activities. That means from locally-linked external drives, HDD, USB drives, SD cards, etc., it is most efficient, not to mention that the interface is nice and quite easy to understand. It is useable right out of the box.

SuperCopier – For wireless connections, NiceCopier seems to slow down, or its performance degrades. Without any change at all of the infrastructure, using SuperCopier does a better job. I used NiceCopier at first, and I find that the countdown goes up and down, and while the file transfer is progressing, there is just no telling when the activity will finish. Thus I used SuperCopier instead, and I am satisfied with the better performance. This is an A-okay application.

Today, I went to search for other applications that may come in handy, or may have other functionalities not present in NiceCopier or SuperCopier, and I found one that I immediately downloaded and installed. When I have used it for some time, I will write a review of it. It is UltraCopier. Hope that it is as good as NiceCopier or SuperCopier, at the very least.

Till then!

Enhanced by Zemanta