IT & Life

Path of the ASP.NET web application that is currently running

System.Web.HttpContext.Current.Request.PhysicalApplicationPath

[Ref: http://www.geekpedia.com/KB44_Get-the-path-of-the-ASP.NET-web-application-that-is-currently-running.html]

Team Foundation Server 2010 Security Permissions

Team Foundation Server (TFS) 2010 is a system not a product and is a combination of WSS, SQL Server and TFS it’s self and most of the Errors and Issues We face during during its Installation and Deployment are releated to SECURITY this might not be possible in every case but if you go online and check this will be the case and that’s what i have learnt during my professional career and deploying TFS multiple times.

We need to understand the following components and the User(s) access rights on them are very important and are the root cause!.

1) SQL Server

a) Reporting Services User rights

b) Analysis Services User rights

c) Database Engine User rights

2) WSS

a) Default Site User rights

b) Central Administration Site User rights

c) Team Site Collection (falling under the Default Site and the Team Sites fall under Team Site Collection) User rights

3) Team Foundation Server

a) Server level User rights

b) Project level User rights

So all these are inter-linked your USER under which your TFS will run has to have rights on all these above mentioned components so let’s say for installation of TFS 2010 you created a user named tfs-user now this User has to have rights on Analysis Services, Reporting Services, SQL DB Engine, WSS sites (Default, Central Admin) and TFS Projects. This is the only way out in which you would be able to deploy, install and configure services rightly and successfully and you would be able to create Team Project successfully and would be able to access Team Site, Reports etc and etc.

So for creating additional users you need to check rights on these specific locations and assign rights as per requirements and privleges.

What to do when Laptop is overheated.

Laptop_overhead

If Windows 3.11 required a 32-bit processor, why was it called a 16-bit operating system?

Commenter Really16 asks via the Suggestion Box how 32-bit Win32s was, and why Windows 3.11 was called 16-bit Windows when it required a 32-bit CPU and ran in 32-bit protected mode.

First, let's look at how Windows worked in so-called Standard mode. Actually, it was quite simple: In Standard mode, Windows consisted of a 16-bit protected-mode kernel which ran applications in 16-bit protected mode. I suspect there would be no controversy over calling this a 16-bit operating system.

With the introduction of Enhanced mode, things got more complicated. With Enhanced mode, there were actually three operating systems running at the same time. The operating system in charge of the show was the 32-bit virtual machine manager which ran in 32-bit protected mode. As you might suspect from its name, the virtual machine manager created virtual machines. Inside the first virtual machine ran... a copy of Standard mode Windows. (This is not actually true, but the differences are not important here. Don't make me bring back the Nitpicker's Corner.)

The other virtual machines each ran a copy of MS-DOS and were responsible for your MS-DOS sessions. Recall that Enhanced mode Windows allowed you to run multiple MS-DOS prompts that were pre-emptively multi-tasked. These other virtual machines ran in a variety of modes, but spent most of their time in virtual-86 mode. MS-DOS applications could use the DPMI interface to switch into 16-bit protected mode, or even 32-bit protected mode if they wanted to. (And that's how Standard mode Windows ran inside the first virtual machine: It used the DPMI interface to switch to 16-bit protected mode.)

It's kind of stunning to realize that Enhanced mode Windows was really a completely new operating system with multiple virtual machines, pre-emptively multi-tasked with virtual memory. In principle, it could have created a virtual machine and hosted yet another random operating system inside it, but in practice the only two operating systems it bothered to host were Standard mode Windows and MS-DOS.

Enhanced mode Windows was called a 16-bit operating system because it ran 16-bit Windows applications (inside a "Windows box", you might say). The supervisor operating system was a 32-bit operating system, but since applications didn't run in supervisor mode, that really didn't mean much. For all anybody cared, the supervisor operating system could have been written in 6502 assembly language. As long as it does its supervisory job, it doesn't matter what it's written in. What people care about is the applications that you could run, and since Enhanced mode Windows ran 16-bit Windows applications, and since it ran a copy of 16-bit Standard mode Windows to do all the things that people considered Windows-y, it was the number 16 that was important.

Besides, you can imagine the uproar from the Slashdot crowd (if Slashdot had existed back then) that an operating system whose purpose is to run 16-bit applications in a 16-bit GUI environment would dare call itself a 32-bit operating system.

How 32-bit was Win32s? Pretty darned 32-bit. A Win32s application ran in the same virtual machine as the rest of Standard mode Windows, but when it ran, the CPU really was in 32-bit protected mode. Naturally, it did all its work under the supervision of the virtual machine manager, and it had to coordinate its work with the Standard mode Windows kernel that it was sharing the virtual machine with. But when your 32-bit application was running, you were bought in: Your registers were 32-bit, your pointers were 32-bit, you accessed data in a 32-bit data segment, and you executed 32-bit instructions out of a 32-bit code segment.

IIS

IIS 4.0 - NT 4.0, Option Pack 4

I remember when I was a teaching assistant at WWU in Bellingham, WA, we were using IIS 3.0; and then I read that IIS 4.0 came out; after talking my professor into it, I installed it and wow, the stability went way up!  Now I didn't need to reboot the server before class in hopes it would last 60 minutes.  :) 

IIS 5.0 - Windows 2000 (Professional & Server SKU's) (use Add/Remove programs -> Windows Components)

When I joined Microsoft, I was part of a team busy doing a re-architecture of IIS (the genesis of the IIS 6 project) while another team finished up IIS 5 and shipped it.  This release was a tough one, because although it added some great features in terms of manageability, it also suffered from a very nasty series of security vulnerabilities.  The IIS team took this very seriously and has to date never forgot the lessons learned.  The early results from that day were URLScan and a super-focus on security.  Today, we still do security reviews of every little feature in IIS and we're constantly trying to break our server.  Also, we stopped installing IIS and it's sub-components by default after this release. 

IIS 5.1 - Windows XP (same as IIS 5 - use Add/Remove programs -> Windows Components)

I remember being frustrated that we had to ship IIS 5.1 (basically a big bug fix release of IIS 5.0) on XP ... I wanted to let everyone see IIS 6.0 because it was so very stable and extremely secure; the timing just didn't work out in the ship schedules.   The other goofy thing is that we actually shipped IIS6 on the 64bit edition of Windows XP which apparently hardly anyone uses. 

IIS 6.0 - Windows Server 2003 

IIS6 was a great release, we spent about 2 and a half years building it; during that time we created a great test infrastructure that we still use to find regressions today.  We became the poster child for how to do secure coding by defense in depth.  In 6 years, we only found 6 vulnerabilities but nothing that was "worm-able" like in the past.  In fact, hackers turned to SQL injection attacks and application-level attacks on the Microsoft platform, attacking poorly written ASP pages and SQL scripts. 

IIS 7.0 - Windows Vista SP1 & Windows Server 2008 (UI) or Windows Server 2008 (command line)

IIS7 was a big change in terms of setup complexity, configuration, and UI.  All three of these changed drastically to allow for complete customizability and extensibility of the web platform.  Now you can add your own components to IIS and get full-featured management support in terms of integration with our configuration and most of our administration tool such as appcmd and our new UI.   

IIS 7.5 - Windows 7 - coming soon!!! 

IIS7.5 is a minor release for our team, basically we integrated several recent out of band projects, added several cool features and of course fixed as many bugs as we could.  Most of the team is working on our IIS extensions and the Web Application Gallery efforts as well as the PHP community efforts.  Still a very cool team to be on and one I hope to stick with in the years to come! 

Asking For a Pay Raise

[Refer: http://jobsearchtech.about.com/od/salary7/a/pay_raise.htm]

Asking for a pay raise might not be easy for you, just as it isn't for most. Even if you eventually muster the courage, there are no step-by-step instructions, sure ways of asking or "magic pills" that guarantee your success. However, following the guidelines below might at least increase your chances.

Asking for a Pay Raise Guidelines

• Before asking for a pay raise, it's important to know that many companies don't grant pay raises to most employees except during employee-review cycles. Additionally, many companies pay competitive, industry-standard wages, which they periodically adjust for cost of living. If you work for one of these companies and you ask for an "out-of-cycle" pay raise or more than the industry standard for your position, your chances for success are likely to be slim.
   
• Check your employee policy manual (or similar document) for information related to asking for a pay raise. For example, if a policy states how to go about it, then follow it to the letter. But if a policy unconditionally states that your employer will not grant an out-of-cycle pay raise, it might be a good idea to stick it out until your next review and request a better-than-usual pay raise. Asking for such a pay raise will probably go over better than trying to buck the system.
   
• It's not a good idea to justify asking for a pay raise by simply stating, "I need the money." It's a much better idea to prove that you deserve a pay raise, by emphasizing your value to the company. Documenting your accomplishments is a good way to do that. For example, you might include your accomplishments in a "presentation" to show your boss, a "cheat sheet" to refer to while negotiating your pay raise, or a letter asking for an appointment to discuss it. Be specific, use examples, and include impressive things like:
  • Revenue you've earned
  • Money you've saved
  • Customer satisfaction you've achieved
  • Tight deadlines you've met or beat
  • Solutions you've implemented
  • Products or services you've improved
  • Initiative you've demonstrated
  • Extra hours you've worked voluntarily

Consider asking for more responsibilities to justify your pay raise. That'll go over better than simply asking for more money, especially if your current responsibilities don't require you to do much above the call of duty and your employer thinks that you're adequately paid.
 

Command a pay raise, don't demand it. For example, you might tell your boss that you'd like to know what you can do to increase your salary or hourly wage in the near future, instead of insisting on a pay raise for your past accomplishments.
 

Think twice about threatening to quit if you don't get a pay raise. It rarely works. No matter how valuable you think you are to the company, don't make the mistake of thinking that you're indispensable. Eager beavers willing to learn your job for less pay are almost always waiting in the wings. If you do quit later for lack of a raise, be careful what you say in your resignation letter so it doesn't bite you down the road.
 

Have a reasonable figure in mind (e.g., from salary surveys) and prepare to negotiate. Be nice but firm when negotiating, and don't get emotional. (Remember, it's business, not personal.) If your employer doesn't grant you a satisfactory pay raise, try negotiating concessions such as performance-based bonuses, or extra paid time off, perks or benefits. Whatever you succeed at negotiating, ask for it in writing with authorizing signatures.
 

Follow the chain of command when asking for a pay raise. For example, if your immediate boss is a supervisor, don't go over your boss's head to the department manager. Instead, approach your immediate boss first and let him or her tell you the next step.
 

A meeting is likely to be more effective than a letter asking for a pay raise. A letter is an inflexible, one-way communication, making it easier for your boss to say no. A meeting is a flexible, two-way communication, that will allow you to present your case as required and overcome objections on the spot. However, a letter will allow you to organize your thoughts, accomplishments and such before presenting them. So, you might consider some combination of the two, such as a letter that highlights your accomplishments to justify your request in the same letter for a pay-raise meeting

HTML http-equiv Attribute

[refer: http://www.w3schools.com/TAGS/att_meta_http_equiv.asp]

 

The http-equiv attribute provides an HTTP header for the information in the content attribute.

The http-equiv attribute can be used to simulate an HTTP response header.

The value of the http-equiv attribute depends on the value of the content attribute.

If the name attribute is set, the http-equiv attribute should not be set.

 

Attribute Values

Value	Description
Allow	Defines the methods supported by the server
Content-Encoding	Defines additional content-encoding for the document
Content-Length	Defines the size of the document (in bytes)
Content-Type	Defines the MIME type of the document (like text/html)
Date	Defines when the document was created
Expires	Defines when the document will be considered obsolete
Last-Modified	Defines when the document was last modified
Location	Defines an absolute URL for the document
Refresh	Defines a time interval for the document to refresh itself
Set-Cookie	Defines a cookie-value
WWW-Authenticate   Note: The attribute value "Refresh" is nonstandard, and should not be used. "Refresh" takes the control of a page away from the user. Using "Refresh" will cause a failure in W3C's Web Content Accessibility Guidelines.	Defines authentication rules returned by the server

MVC vs. MVP

[Refer: http://www.darronschall.com/weblog/2004/06/mvc-vs-mvp.cfm]

MVC came first. With the MVC pattern it's possible to separate your presentation information from your behind the scenes business logic. Think along the lines of XHTML/CSS and separating your content from your presentation. A brilliant concept that works quite well, but is not without it's faults.

In MVC, the model stores the data, the view is a representation of that data, and the controller allows the user to change the data. When the data is changed, all views are notified of the change and they can update themselves as necessary (think EventDispatcher).

MVP is a derivative of MVC, mostly aimed at addressing the "Application Model" portion of MVC and focusing around the observer implementation in the MVC triad. Instead of a Controller, we now have a Presenter, but the basic idea remains the same - the model stores the data, the view is a representation of that data (not necessarily graphical), and the presenter coordinates the application.

In MVP the Presenter gets some extra power. It's purpose is to interpret events and perform any sort of logic necessary to map them to the proper commands to manipulate the model in the intended fashion. Most of the code dealing with how the user interface works is coded into the Presenter, making it much like the "Application Model" in the MVC approach. The Presenter is then directly linked to the View so the two can function together "mo' betta".

Basically, in MVP there is no Application Model middle-man since the Presenter assumes this functionality. Additionally, the View in MVP is responsible for handling the UI events (like mouseDown, keyDown, etc), which used to be the Controllers job, and the Model becomes strictly a Domain Model.

SQL variable template

In Scripts:

use <@target_db,varchar,(input db name here)>

 

1. Press <Ctrl> + <Shift> + M
2. Enter variable for template
3. Done

 

 

 

小心婚前6大雷區！

百年修得夫妻緣，可別讓小小的細節問題誤了終身！不妨看看《大日子》列出的婚前6大雷區，以免誤闖。

1 爭吵

雙方產生矛盾，由小變大，由芝麻綠豆膨脹成鋪天蓋地，罪魁禍首往往就是「爭吵」。

這是婚前經常發生的問題，也是最嚴重的問題。

談戀愛時雙方偶有拌嘴，男方往往會比較大度的遷就。一旦真正進入結婚準備期，直接面對人生大事了，女方眼裏往往容不得半粒沙子，甚至鑽牛角尖。平時看起來可愛的玩笑或者偶爾的打情罵俏，在心情格外煩躁激動的日子裏，往往會被誤解為其他含義，一些無傷大雅的小問題，如約會遲到、電話未接等，也可能成為不能容忍的矛盾。其實結婚本就是兩個不同的個體生活在一起，必定會產生摩擦和矛盾。重在調整好心態─ 既然已經決定了對方為終身伴侶，可不要因為一些瑕疵而否定了整塊美玉。

矛盾根由：

過於糾纏過火的玩笑、遲到、忘記約好的事等一些細小的事情，被一時的情緒控制了整個心態。

應對方案：

放鬆心情，調整心態，平靜面對自我的真實感受，擺脫情緒的一時控制。

2 生活習慣

新婚在即，是否已經幻想起了婚後甜蜜幸福的生活？是月光下二人相偎相依，綿綿蜜語在耳邊淌過；或者是回到家後驚喜地燭光晚餐，雖然看似並不美味，但入口卻別有一番回味。這些只是婚姻生活美好的一部分，如果你看到的是滿地亂放的襪、衣服，浴室用完沒有歸位的用具， 廚房裏還未清洗的鍋碗瓢盆和賴在沙發上看電視的那個人，你是否有想結束這種生活的衝動呢？為了體驗、適應婚後生活，許多男女往往在舉辦婚禮前就同居試婚，也正是因為如此，生活習慣的不同讓對方心理產生巨大的落差，這段試婚生活也以此作為終點了。

矛盾根由：生活習慣不同、生活分工不明確

應對方案：為了保持生活和諧，雙方要從戀愛轉向婚姻生活，可以向父母討教雙方生活的訣竅，對家庭中的事物進行分工，對對方生活中的小習慣持包容和認真地心態加以指正。

3工作因素

結婚籌備期長，真正的儀式只不過短短一天，在工作壓力巨大、工作節奏極快、工作競爭激烈的社會，要新人們利用空餘時間好好準備婚禮確實是一件非常頭疼的事。雖然現在有專業的公司替你辦妥，但很多細節的事還需要親自動手。在準備婚禮和工作之間，往往會產生衝突，雙方中的一方因為工作而不能很好的參與準備，加上沒有良好的溝通，那另一方快樂的心情霎時即被沖淡，分道揚鑣的念頭隨即滋長。

矛盾根由：

一方因為工作而忽視了對方，使對方過多承擔了責任，且沒有良好的互動溝通

應對方案：

在結婚準備前，雙方應根據工作和空餘時間安排進行計畫和分工，如遇突發情況應儘快與對方溝通，互相幫助，避免準備不及時和對方的埋怨。

4 婚禮中的差錯

作為新娘，最大的心願就是希望有一次完美的婚禮，但人非聖賢，孰能無過，完美的婚禮需要天時、地利、人和，偶爾的小差錯何必放在心上，破壞婚禮的氣氛呢？堵車、壞天氣、忘記道具等事情，在新娘眼裏都是破壞夢想婚禮的兇手，由於這些小問題，心情變得極度糟糕，牽連新郎、家人，甚至影響結婚的進程。矛盾根由：過於看重婚禮當天的表現

應對方案：盡人事，知天命，婚前儘量安排好細節工作，預料到可能出現的差錯，雙方

共同解決，如無解決辦法，那就忽略，把這當成是上天給你的安排，自有他的道理。

5家人磨合

結婚不僅僅是兩個人的事，更是兩個家庭的事。

許多愛情，往往在最終階段由於彼此的家庭矛盾而凋謝，終難成就正果。作為結合的一對，站在自己家人和愛人的立場從中調解周旋才是保證婚姻生活圓滿的基礎。現實生活中往往不是如此，都是養育自己幾十年的父母、相處二十幾年的兄弟姐妹，都希望結婚能夠順應家人的意願。但是兩家人往往有不同的想法，女方喜歡氣派；男方喜歡溫馨，對婚宴不同的要求自然讓兩家的長輩互生芥蒂······男方和女方夾在中間，一不小心可能導致一拍兩散的結局。

矛盾根由：

缺乏心理互換立場；缺乏做好「中間人」的技巧。

應對方案：

1 . 男女雙方應多安排雙方父母見面，交流感情，對父母合理的要求和建議予以考慮，不要一味遷就自己的父母或對方；

2 . 對於比較難於融合的矛盾，要講究溝通技巧，儘量規避雙方的直接正面接觸，而由自己充當中間人加以調和；

3 . 自己家人情緒激動時說出來的「晦氣話」，往往成為傷害對方感情的利刃，所以要儘量避免傳遞給對方。

6心態變化

結婚後往往都會覺得你的另一半似乎變了，以前的體貼細緻、善解人意似乎在一點點消失，從前的溫柔瀟灑、專注用心也似乎一去不復返，究其原因是雙方心態的變化。從單身到結婚，也許意味著人的成熟，也許也意味著浪漫和用心的消逝。一旦要步入婚禮的殿堂，對兩人關係的要求、行為的出發點就會產生變化：她/他不是你的女朋友或者男朋友，而是你的妻子/丈夫，所以你似乎有權力可以指揮她/他做一些事情， 似乎可以不用再細心的打扮、精心的準備， 似乎你覺得他/ 她應該負更多的責任，而你有更多的要求等待她/他完成······是人變了嗎？不是，是心態、身份不同了。

矛盾根由：

戀愛與婚姻沒有很好地過渡

應對方案：

婚後側重點雖然是生活，但是婚姻同樣需要滋潤，兩個人共同的生活需要更多的心思來設計。不要把「實實在在地生活」理解為「死死板板地過日子」，也不能把婚姻當做某種權利濫施濫用。