IIS bug with ASP.NET

In the name of ALLAH

when i tried to build my first ASP.NET 2.0 Application
with visual studio 2005 and IIS 5.0
i begin with installing the IIS on my computer and i start to create new web site
with HTTP location
hmmm suddenly i shocked with this error

configuring web site 'http://localhost/ webtime' to ASP.NET 2.0 failed. you
may need to manually configure this site for ASP.NET 2.0
in order for your site to run correctly

and when i tried to run my application my browser shows that:

The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the
error and
then click the Refresh button, or try again later.

A name was started with an invalid character. Error processing resource
'http://localhost/ WebTime/WebTime. aspx'. Line 1, P...
<%@ Page Language="c# " AutoEventWireup= "true"
CodeFile="WebTime. aspx.cs"
> Inherits="WebTime"


i spent about 2 weeks trying to solve this disturbing problem
I'm sure that my code is correct 100%
i uninstalled and reinstalled VS 2005 and IIS many times without any improvement
finally i find it every time i unistalled VS and IIS i install the VS first then IIS
this time i installed IIS first then VS 2005
this time the first error exploded or in other words it didn't appear it's gone
that's great nice step
but also when i tried to run my application the second error changed with unfamiliar
error in the browser page that error as i remember was XML parser error
hmmm that mean the problem doesn't solved yet
after that i decided to repair my framework 2.0 application from add remove programs
wooooow that's it here is the solution
that solve the problem
i don't know where is the problem and what's make that but i just know that will
solve the problem.
just install IIS first then VS 2005
then go to add remove programs in control panel and repair
framework 2.0 package and that's all.
enjoy.

The underwater world of Antarctica

In the name of Allah
i saw this pictures on the web and i really can't believe my eyes
what a beauty place i can't say any thing more than "sobhan Allah" glory to Allah!

Battle at Kruger

In the name of Allah
my friend ahmad gamal has send this great video to me.
it's the most strange video you can see in the kruger life
this's the video

Hallmarks of a Great Developer

in the name of Allah

that's some tips to be a good developer

i found it on this blog:
http://blogs.msdn.com/micahel/archive/2004/06/16/157202.aspx

Plans before coding

A great developer takes the time to plan an approach before designing or coding. A great developer knows that the time required to do so will be more than paid back by the time saved by getting it more right the first time. A great developer plans all scales of work, from envisioning multiple versions of a product to writing or modifying a small method.

Always knows why

A great developer always knows exactly why they wrote a particular line of code, and why they wrote it the way they did. A great developer writes code because that code is the best choice for a particular situation, not just because it is the canonical implementation. A great developer codes consciously.

Writes situation-appropriate code

Any developer can write code. A good developer writes solid code. A very good developer writes elegant code. A great developer writes code that is both solid (compact, well constructed) and elegant (precise, simple, graceful, polished). More importantly, a great developer can tell when elegance is not worth the effort.

Deviates where and when necessary

A great developer not only knows the canonical implementation but understands it is the canonical implementation. A great developer can tell when the canonical implementation is not the best answer for a particular problem.

Knows when not to change code

A great developer knows that changing code is sometimes worse than fixing it. Fixing a bug may cause too much instability elsewhere in the product, for example. Messy code whose function is not well understood shouldn't be rewritten until there is sufficient time to ensure its function is well understood. A great developer understands the tradeoffs involved between changing code versus leaving it as is.

Approaches debugging scientifically

A great developer knows that debugging is a science not an art and approaches it as such. A great developer formulates a theory as to the cause of the problem, determines a method for proving the theory wrong, performs the experiment, and observes the result. A great developer records this information and uses this data to guide further work.

Walks through their code

A great developer knows that they don't really know their code until they've stepped through it. A great developer sets breakpoints on every line of code as it's written so they know which lines haven't been hit.

Knows the language and platform intimately

A great developer knows the programming language (and platform) in use inside and out. A great developer knows why each construct (API) was included in the language (platform) and why other constructs (APIs) were left out. A great developer disagrees with certain aspects of the language (platform) but understands why those aspects work the way they do. A great developer knows what the language (platform) can do, what it can't, and how to achieve the same effect through other means.

Groks the tools

A great developer knows what the available tools are and how to use each of them. A great developer knows that not every tool is appropriate for any particular task. A great developer knows how to abuse the tools to produce results hard or impossible to accomplish via "approved" uses.

Improves the tools

A great developer knows that their tools can always be improved. A great developer prefers to get these improvements from elsewhere so they can concentrate on solving the customer's problem. A great developer recognizes when it is simply faster or more efficient to write a tool themselves. A great developer constantly looks for opportunities for increasing their productivity.

Knows when to ask for help

A great developer takes pleasure in a challenge. A great developer, then, enjoys banging up against a brick wall and slowly breaking through it. Some walls are thicker than others, however, and sometimes the wall has a developer-size hole that the developer continually manages to miss. A great developer realizes when it's time to ask for help and does so. A great developer knows who to ask for help. A great developer knows there isn't any shame in asking for help.

Always has a side project going

A great developer is never completely satisfied by the current project. A great developer is always also working on a (probably many) side project meant to investigate an idea, understand a language or library feature, automate a process, or otherwise itch a scratch the primary project isn't satisfying.

Doesn't make assumptions

A great developer actually does make assumptions, but a great developer doesn't stop there. A great developer inspects the assumption, then researches that assumption into knowledge. A great developer does this not just for their own assumptions but for assumptions other people make as well.

Documents

A great developer documents everything. A great developer strives for self-documenting code but knows that some amount of documentation is always required. A great developer knows that documentation need satisfy only two goals: educate the current audience, and preserve enough knowledge about the topic that the current audience can expand the documentation as necessary for any future audience.

Follows coding standards

A great developer has internalized and continuously uses a set of coding standards. A great developer may not be able to recite the standards word for word, but when asked about any particular point the correct answer is immediately forthcoming. A great developer writes conformant code without the aid of verification tools, but always runs those tools as a backstop.

Uses version control

A great developer knows that version control is as important for personal projects as for enterprise projects. A great developer version controls everything.

Makes lots of small checkins

A great developer knows that version control is most useful when code is modified via small checkins that each contain a single logical change. A great developer strives to check each change in independently from each other change.

Tests their own code

A great developer is embarrassed when someone else finds a bug in their code. A great developer thoroughly tests their code before checking it in. A great developer doesn't pretend to be a great tester but does strive to be considered a good tester.

Has passion for their customer

A great developer understands what the customer needs to do and how the customer wants to use the product. A great developer looks beyond the customer's needs to see how the product can revolutionize the customer's tasks. A great developer promotes the customer's point of view throughout the product cycle, from the first nascent product vision through specifying and implementing features to cutting features and triaging bugs to product release and ongoing maintenance. A great developer helps the rest of the product team understand the customer as well as they do.

Has great judgement

A great developer understands the business case for the code he is writing. A great developer uses this as a basis for judging what code to write and what code should not be written. A great developer uses this as a basis for deciding when to write code and when writing code is not the right thing to do. A great developer uses this to balance designing for the future against the need to get something done in a timely manner.

Has no ego

A great developer values the praise of their customer over the praise of their peers. A great developer wants to do the right thing but doesn't much care about being right. A great developer brings their reasoned opinion to design and coding discussions but listens carefully when alternatives are offered, searching out and examining the details of these other options. A great developer appreciates suggestions for improving their code or design. A great developer knows they will write bugs and appreciates it when bugs are brought to their attention. A great developer follows a process because the process protects them from themselves.

Makes time for training

A great developer knows that the only way to continue to be a great developer is to never stop learning. A great developer doesn't limit this education to programming-related topics, either, but also researches testing, program management, marketing, and anything else that is remotely related to the process of creating software.

can't access tty in Ubuntu Feisty Fawn Live CD

This title is an error occurred when i tried to boot from Ubuntu Feisty Fawn Live CD
before about one week.
it listen to me that error occurred for many people
specially those who have more than one hard disk

this is the exact error:
/bin/sh: can't access tty; job control turned off

i lost many time in that problem but finally i fixed it.
the solution of this error for those who have more than one hard disk is that
first unplug all the hard drives except the one you will install ubuntu on it
then try to boot again from the CD it should boot well,
but the problem is not fixed yet,
after you are in ubuntu you should type this in terminal :

sudo gedit /etc/initramfs-tools/modules

and then add this to the end of the file

piix

and then save the file and type this in terminal :

sudo update-initramfs -u

now turn off your PC , and then connect your other drives cables again and start ubuntu , it should work fine !

but what about if there where just one hard drive ?

in this case if you have floppy disk unplug it and type the above terminal commands

else i read some where that you should change your usb settings in the bios settings
to usb 1.0 instead of 2.0 ,but I'm not sure.

hope this be helpful.
enjoy.

i have 65% internet information

youtube for muslims

in the name of Allah

i found a great site for islamic videos.
no more prohibited videos.
that's the site: http://www.muslimvideo.com
check it and enjoy it.
that's one of it's great videos.
the home page of this video

that video about the opening speech of AL HEKMA islamic channel

Back

.....OH my blog again,
that's a long time since i visited this place,
i was decided to not visit it again
becuase i'm not a good blogger
i'm not a good speaker
i wasn't think that i will find some thing to publish on it,
but i dicovered that there is alot of things to talk about here,
why i didn't make this blog like a friend and tell him about me,
about my life,
and about my dreams.
specially when i don't find a trusted friend to speak with him.
so i decided to back and to dicovering my self via this blg.
i hope to sucsess in that.....

Introduction

In the name of Allah the most Gracious and the most Merciful

Beginning I hope this blog to be a light stand for all people,
and i hope from Allah to grant me the success to achieve my dreams
my dreams to success in my study,
my dreams to build my country again,
and my big dream to be one of the winners in the Day of Resurrection.