Friday, November 15, 2013

How to change user credentials for TFS in Visual Studio 2012



Hi, Today one of my developer reported that whenever he check-in/ check-out files in visual studio it showing different username(Actually its admin username)Now I came to know that once myself connected tfs server on his pc for troubleshooting some other issue.
 
Now I try to find out how to change user credentials for TFS in visual studio. After researching little bit time I found that how to change user credentials for TFS in VS 2012.
I thought if I blog this post it will help someone like same situation.
This article is explaining about how to change or clear credentials which are used to connect Team Foundation Server from Visual Studio 2010 and Visual Studio 2012.
TFS credentials
    When you connect TFS from Visual Studio you will be asked to give user credential to connect. If you checked the option Remember my credentials while connecting TFS, you won't be asked credentials again to connect TFS. In that case, if you wanted to change different credentials to connect TFS. you need to follow below solution to force Visual Studio to ask new credentials to connect TFS.

   


Force to change TFS credentials in Visual Studio
     You need to remove TFS credentials from Windows Vault to clear and force to ask new TFS credentials in Visual Studio

      1. Go to Control Panel (Start -> Control Panel).

      2. Click User Accounts ( or User Accounts and Family Safety->User Accounts in Windows 7 Machine)

      3. Click Credential Manager (or Manage your credentials)
 


 
     4. In Credential Manager page, you can see the two type of credentials

           i. Windows Credentials
           ii. Generic Credentials

     5. Click on two credential's modify link,  click the link Remove from vault to remove stored TFS credentials.

Now, When you login into Visual Studio you will be asked to give credentials to connect TFS.

Note: Don't forget to uncheck the option Remember my credentials to force to ask credentials for every TFS connections.

If you find this is helpful post then leave your comments...


Regards
R.karthikeyan 

Friday, November 1, 2013

Microsoft Free voucher for the exam


Add Hyper-V to your server virtualization skillset and improve your career options: Register for this free course, led by Microsoft experts Symon Perriman and Telmo Sampaio: Server Virtualization w/ Windows Server Hyper-V & System Center Jump Start.


This course helps you prepare for the new Microsoft virtualization certification: Microsoft Specialist Exam 74-409-Server Virtualization with Windows Server Hyper-V and System Center. Event attendees will get a free voucher for the exam*

Already familiar with other virtualization platforms such as VMware or Citrix? Upgrading virtualization platforms?  New to virtualization?  If any of these are true, then this course is intended for you. Get expert instruction on Microsoft Server Virtualization with Windows Server 2012 R2 Hyper-V and System Center 2012 R2 Virtual Machine Manager in this two-day Jump Start. You will learn how to configure, manage, and maintain Windows Server 2012 R2 Hyper-V and System Center 2012 R2 Virtual Machine Manager including networking and storage services. You will also learn how to configure key Microsoft server virtualization features such as Generation 2 Virtual Machines, Replication Extension, Online Export, Cross-Version Live Migration, Online VHDX Resizing, Live Migration Performance tuning as well as Dynamic Virtual Switch Load Balancing and virtual Receive Side Scaling (vRSS). 

Server Virtualization w/ Windows Server Hyper-V & System Center Jump Start

  • Date:  November 19 & 20, 2013
  • Time: 9:00am – 4:30pm
  • Where: Live, online virtual classroom
  • Cost: Free! 

Put your career in hyperdrive and Register now.

 Additional Resources:

 *The number of free exams is limited, so be sure to schedule your appointment to lock in your free exam. Vouchers expire and all exams must be taken by June 30, 2014.

Regards
R.karthikeyan

Friday, October 18, 2013

Visual Studio 2013 available for download




I’m excited to announce that the final releases of Visual Studio 2013, .NET 4.5.1, and Team Foundation Server 2013 are now available fordownload!  MSDN subscribers can download from the MSDN Subscriber Downloads page.

Visual Studio 2013 is the best tool for developers and teams to build and deliver modern, connected applications on all of Microsoft’s platforms.  From Windows Azure and SQL Server to Windows 8.1 and Windows Phone 8, Visual Studio 2013 supports the breadth of Microsoft’s developer platforms.
As part of the Cloud OS vision, Visual Studio 2013 enables developers to build modern business applications that take advantage of the cloud and target a variety of devices and end-user experiences, all delivered within today’s rapid and dynamic Application Life Cycles.
  




More Information on Somasegar’s blog


Regards
R.karthikeyan

Monday, October 14, 2013

Waterfall Model vs Agile Methodology



Introduction
Waterfall model follows application development in phases with checkpoint and deliverable documents in each checkpoint. It advocates rigours project management, strategy and processes to track the status. The main drawback is that it requires more than 80% project understanding before kicking off the project which is impossible in major cases. Cause of volatile requirements and understanding business feels, 80% of software projects using this methodology fail to meet their objectives.
Typical Waterfall Model




Agile Methodology
Agile mythology has small box iterations rather than phases. The output of each iteration will be production release deliverable and could be evaluated and get early feedback.
Agile was a significant departure from the heavyweight document-driven software development methodologies—such as waterfall—in general use at the time.
Agile refers to more collaboration and interaction between different departments at enterprise level and delivers the successful product with individual contribution.
Agile methodologies embrace iterations. Small teams work together with stakeholders to define quick prototypes, proof of concepts, or other visual means to describe the problem to be solved. The team defines the requirements for the iteration, develops the code, and defines and runs integrated test scripts, and the users verify the results. Verification occurs much earlier in the development process than it would with waterfall, allowing stakeholders to fine-tune requirements while they’re still relatively easy to change.
It promotes adaptive planning, evolutionary development & delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change.


 

 
XP (Extreme Programming
It advocates frequent “release” in short development cycles, each release follows with several iterations. When the product release has enough features to satisfy the user, the team terminates iteration cycle and releases the software.
Other elements of Extreme Programming include: programming in pairs, continuous integration, add only needed features for a particular release.
Users write a story which helps the team to estimate the time to build the release and to define acceptance testing. A user is a part of XP team and adds the detail requirement as the software is being built. This allows requirements to evolve as both users and developers define what the product will look like.






  • Continuous Integration: Integrate often at least once a day using automated continuous integration tool
  • Pair Programming: Pair programing to extensively code review while coding
  • Project velocity: Velocity is a measure of how much work is getting done on the project. This important metric drives release planning and schedule updates.
Scrum
Scrum is a way for teams to work together to develop a product wherein requirement changes rapidly during development. Product development, using Scrum, occurs in small pieces, with each piece building upon previously created pieces. Building products one small piece at a time encourages creativity and enables teams to respond to feedback and change, to build exactly and only what is needed. Unlike XP, Scrum methodology includes both managerial and development processes.






  • Sprints: Short development process
  • Stand up meeting: Daily 10 minutes meeting status of the work to be done that day, progress from the day before, and any blocks that must be cleared
  • Scrum Master: The ScrumMaster is the person responsible for managing the Scrum project
  • Sprint backlog: Sprint backlog is the list of backlog items assigned to a sprint, but not yet completed.
  • Burn down chart: This chart, updated every day, shows the work remaining within the sprint. The burn down chart is used both to track sprint progress and to decide when items must be removed from the sprint backlog and deferred to the next sprint.
  • Product backlog: Product backlog is the complete list of requirements 


Agile: The Pros
Agile offers an incredibly flexible design model, promoting adaptive planning and evolutionary development. Agile might be described as freeform software design. Software developers work on small modules at a time. Customer feedback occurs simultaneously with development, as does software testing. This has a number of advantages, especially in project environments where development needs to be able to respond to changes in requirements rapidly and effectively.

Agile can be especially beneficial in situations where the end-goals of projects are not clearly defined. For example, if you are working with a client whose needs and goals are a bit hazy, it is probably worthwhile to employ the Agile method. The client’s requirements will likely gradually clarify as the project progresses, and development can easily be adapted to meet these new, evolving requirements. Agile is also an excellent option for experimental software design.

Lastly, this method also facilitates interaction and communication – collaboration is more important here than design. Because interaction among different designers and stakeholders is key, it is especially conducive to teamwork oriented environments. Different developers work on different modules throughout the development process and then work to integrate all of these modules together into a cohesive piece of software at the end of the project.

Waterfall: The Pros
The emphasis of Waterfall is the project plan and therefore before beginning any kind of development there needs to be a clear plan and a clear vision in order. Because the Waterfall method requires upfront, extensive planning, you can launch software fairly quickly. You can also estimate timetables and budgets more accurately, which definitely tends to please clients.

Furthermore, Waterfall development processes tend to be more secure because they are so plan oriented. For example, if a designer drops out of the project it isn’t a huge problem, as the Waterfall method requires extensive planning and documentation. A new designer can easily take the old designer’s place, following the development plan without a problem.

Agile: The Cons
Though highly flexible, Agile simply doesn’t have the structure that the Waterfall method has and this does present some drawbacks. Agile projects tend to be hard to predict, from timelines to budgets. Without a concrete plan, everything remains a bit vague and nebulous.

In addition, as previously discussed, active user involvement and intense collaboration are required throughout the Agile process. This can prove highly problematic for a number of reasons. First of all, this method of development can be quite time consuming, much more time consuming than the Waterfall method. And, it means that designers need to be committed for the duration of the project. If a designer leaves in the midst of a Waterfall method development project, it likely won’t be too big of a deal as the project is plan based. In the case of the Agile method, however, development is much more person based. Having a person drop out of the project could prove catastrophic.

Waterfall: The Cons
The Waterfall method is incredibly rigid and inflexible. Altering the project design at any stage in the project can be a total nightmare and once a stage has been completed, it is nearly impossible to make changes to it. So, if you’re planning to use Waterfall, you will need to gather all of the requirements upfront. In addition, the problem with the Waterfall method is that feedback and testing are deferred until very late into the project. So if there is a problem, it is very difficult to respond to it, requiring a substantial amount of time, effort, and sometimes money.

So, What’s Better?
When it comes down to it, neither the Agile method nor the Waterfall method is inherently better than the other. That being said, each method does have its uses. Waterfall tends to be best for static projects, where it’s not likely that many changes will be made throughout the development process. In contrast, Agile tends to be a better option for smaller projects where changes are likely to be made during the design process. Though, keep in mind that these are just rough guidelines and suggestions. Really, when it comes to choosing a method there is not a right or wrong choice. You just need to understand which method is better suited to your project and your needs.



Thanks
R.karthikeyan

Share this

Labels

WINDOWS SERVER (22) Windows (20) IIS (15) Interview questions (10) TFS (9) Troubleshooting Tips (9) Fortigate Firewall (8) SQL (8) Backup (6) Team Foundation Server (6) Webserver (6) Windows Administration Task (6) Microsoft certification (5) Virtualization (5) ADDS (4) Active Directory (4) FTP (4) PHP (4) SQL 2012 (4) SQL Server (4) server (4) DBA (3) MSSQL (3) Networking (3) Offer (3) Webhosting (3) Windows 8 (3) 74-409 (2) Agile Methodology (2) Apache (2) CLI Commands (2) DNS (2) Dedicated server (2) Difference between Active and Passive Connection Mode (2) Fortinet (2) GPO (2) IIS8 (2) IPAddress (2) IPV6 (2) MVA (2) Microsoft News (2) NAT (2) Software Development (2) TFS2013 (2) Uncategorized Post (2) XAMPP (2) firewall Administration. (2) powershell (2) .htaccess (1) ALM (1) Agile vs Scrum Difference (1) Blogging TIPS (1) CPanel (1) Command for Administrator (1) DC (1) DHCP (1) Domain joining nano server (1) Exam 74-409 (1) Excel TIps (1) File server (1) Fortigate Firewall HA (1) Fortigate Firmware Upgrade (1) Free Exam 70-740 (1) Free Voucher (1) Generation2 VM (1) Group Policy (1) HP (1) HP ILO IP CHange (1) HP OA IP Change (1) HP Proliant Servers (1) HTTP to HTTPS (1) Hyper-V (1) IAS (1) IIS Server hardening (1) ILO (1) Install dll (1) MCSA 2016 (1) Microsoft Virtual Academy (1) Microsoft file sharing Port (1) Migration (1) MySQL (1) NPS (1) Nano server (1) Network Drive (1) OA (1) Plesk Panel (1) Ports (1) Ports for windows file sharing (1) RADIUS (1) RDP (1) Remote Desktop Connection (1) SCRUM (1) SQL ErrorLog (1) SQL TEMPDB (1) Second Shot (1) Server 2012 (1) Startup Parameters (1) TEMPDB Movement (1) TIPS (1) Team Foundation Server 2013 (1) Temp profile. (1) Troubleshooting DNS (1) URL Rewriting (1) VDOM (1) VPS (1) VSS (1) Virtual Labs (1) Visual Studio (1) Visual Studio 2012 (1) Visual Studio 2013 (1) Visual source safe (1) Waterfall Model vs Agile Methodology (1) Windows 2016 (1) Windows 7 (1) Windows Server 2012 (1) Windows command line (1) XP (1) certification path (1) exam (1) free online courses (1) protocols/ports for windows file sharing on a firewall (1) sql error (1) what features has been installed in your SQL Server (1) windows 2012 (1) windows Time Service (1) work item types difference (1)

E-Books

Blogger Gadgets