A very attractive article on Google Search by Mark Wagner's
http://tech.groups.yahoo.com/group/MSTechnologies/message/5
http://blogs.crsw.com/mark/articles/1009.aspx
Monday, June 30, 2008
Thursday, June 26, 2008
INFO-IE: Ensuring your website is ready for Internet Explorer 8 - IMPORTANT
Please consider this as an important read. Consistent with Microsoft efforts to promote further interoperability across the Web, Microsoft will be releasing Internet Explorer 8 to render content in its most standards-compliant way by default. Giving top priority to Web standards interoperability allows us to help web developers and designers drive toward the ideal of "write once, run anywhere", freeing up more time to innovate rather than modify content for different browsers. This commitment also addresses several development and design pain points from previous Internet Explorer releases.
However, browsing with this default setting may cause content written for previous versions of Internet Explorer to display differently than intended. This creates a call to action for site owners to ensure their content will continue to display seamlessly in Internet Explorer 8. As such, we have provided a meta-tag usable on a per-page or per-site level to maintain backwards compatibility with Internet Explorer 7. Adding this tag instructs Internet Explorer 8 to render content like it did in Internet Explorer 7, without requiring any additional changes.
We are encouraging site administrators to get their sites ready now for broad adoption of Internet Explorer 8, as there will be a beta release in the third quarter of this year targeted for all consumers. To learn more and get started, please follow the step-by-step instructions located at the following link: http://go.microsoft.com/fwlink/?LinkId=120024 .
Additional Resources
The following links provide additional information you may find useful:
· Internet Explorer 8 main site: http://www.microsoft.com/ie/ie8
· Internet Explorer Team Blog: http://blogs.msdn.com/ie
· Internet Explorer Developer Center: http://msdn2.microsoft.com/en-us/ie/default.aspx
· Internet Explorer 8 Readiness Toolkit (for web designers and developers): http://www.microsoft.com/windows/products/winfamily/ie/ie8/readiness/default.htm
· Microsoft Interoperability Principles: http://www.microsoft.com/interop/principles/default.mspx
However, browsing with this default setting may cause content written for previous versions of Internet Explorer to display differently than intended. This creates a call to action for site owners to ensure their content will continue to display seamlessly in Internet Explorer 8. As such, we have provided a meta-tag usable on a per-page or per-site level to maintain backwards compatibility with Internet Explorer 7. Adding this tag instructs Internet Explorer 8 to render content like it did in Internet Explorer 7, without requiring any additional changes.
We are encouraging site administrators to get their sites ready now for broad adoption of Internet Explorer 8, as there will be a beta release in the third quarter of this year targeted for all consumers. To learn more and get started, please follow the step-by-step instructions located at the following link: http://go.microsoft.com/fwlink/?LinkId=120024 .
Additional Resources
The following links provide additional information you may find useful:
· Internet Explorer 8 main site: http://www.microsoft.com/ie/ie8
· Internet Explorer Team Blog: http://blogs.msdn.com/ie
· Internet Explorer Developer Center: http://msdn2.microsoft.com/en-us/ie/default.aspx
· Internet Explorer 8 Readiness Toolkit (for web designers and developers): http://www.microsoft.com/windows/products/winfamily/ie/ie8/readiness/default.htm
· Microsoft Interoperability Principles: http://www.microsoft.com/interop/principles/default.mspx
Wednesday, June 25, 2008
Microsoft identifies tools to address SQL injection attacks
Microsoft is alerting customers to several tools that could bolster Web application development in the wake of a rising number of SQL injection attacks targeting faulty code in websites.
http://searchsecurity.techtarget.com/news/article/0,289142,sid14_gci1318731,00.html?track=NL-102&ad=641700HOUSE&asrc=EM_NLN_3916392&uid=1709793
By Robert Westervelt, News Editor
24 Jun 2008 SearchSecurity.com
http://searchsecurity.techtarget.com/news/article/0,289142,sid14_gci1318731,00.html?track=NL-102&ad=641700HOUSE&asrc=EM_NLN_3916392&uid=1709793
By Robert Westervelt, News Editor
24 Jun 2008 SearchSecurity.com
Monday, June 16, 2008
The Problem with IT Project Management (an Article by ZapFlash)
The Problem with IT Project Management
Document ID: ZAPFLASH-2008612 Document Type: ZapFlash
By: Ronald Schmelzer
Posted: Jun. 12, 2008
One of the most challenging aspects of Enterprise Architecture (EA), and Service-Oriented Architecture (SOA) in particular, is that rather than address a discrete problem or set of problems in the enterprise, it attempts to address a range of interconnected and perplexing issues that have long troubled IT. Specifically, SOA approaches to EA address long-term issues of integration in environments of continued heterogeneity, application development in the face of continuous change, governance, management, and quality in environments of continuous complexity, increasing reuse and reducing redundancy across multiple IT initiatives, and organizational and methodology approaches that favor iteration over monolithic, waterfall-style approaches to development.
While none of these challenges are new, and in fact, many architects have a number of tools, techniques, and approaches at their disposal to address those issues, EA attempts to address them in a holistic manner, providing a consistent approach to use in the face of continued business and technological change. One of the biggest impacts of this holistic approach to IT management is that discrete IT project management is rapidly going by the wayside. This doesn’t signal the death of IT project management, but it does suggest that evolving approaches to EA require changes not just in technology and application development approach, but also changes in the way in which we manage the organization’s overall evolution given that it will become harder to distinguish between development of individual IT projects and advancement of individual IT resources.
The End of the Discrete IT Project
Most corporate IT environments have significant complexity. Even if the set of systems and applications are small in number, their interconnections, customizations, and dependencies quickly evolve into a morass of complexity referred to as the "IT rat’s nest". Into this environment of IT complexity, the business continues to impose their requirements and changes, resulting in the creation of yet more IT resources, interconnections, customizations, and dependencies. This web of complexity quickly becomes so thick that any change to one part of the environment, say a data schema changes, has ripple effects throughout the whole of the organization. Like a game of pick-up-sticks, nothing can move without moving the whole pile.
Yet, most companies still do traditional IT project management in which the requirements are defined and budgets set as if that IT project has no interaction with any of the other IT projects and resources that already exist in the company. In an environment where the web of complexity exists, the notion that you can pick up an "IT stick" without disturbing the rest of the pile makes no sense. One of the prime reasons why many IT projects go over time and budget is because the requirements that seemed simple turn out to be more difficult than anticipated. Some of the difficulty comes from imprecise definition of requirements, but the majority of the challenge comes from realizing how one requirement impacts the system as it already exists. "The Devil’s in the details", as is often said with IT project management, and the Devil is complexity.
Companies that have no plans to do any sort of heterogeneous application development or composition, or who have the time and budget they need to deal with constantly expanding projects in the face of continuously expanding complexity can afford to do discrete IT project management. But for the rest of us, any movement we make to try to bring the organization’s systems together into a predictable, composable, governed, loosely-coupled, and potentially reusable set of assets, or in other words, to apply any real Enterprise Architecture, will require that we stop doing IT project management in a discrete fashion and treat IT as a continuously evolving asset.
Lessons from Human Resources and Finance
Vendors, consultants, and end-users alike over-use and abuse the "Business-IT alignment" refrain without truly understanding what it takes to bring IT into alignment with the rest of the business. Simply facilitating the business requirements to IT implementation generation process is not enough to really turn IT into an asset rather than a cost center. Rather, what’s required is shifting the responsibility for the application of IT to the business and changing the organizational and funding model to reflect the role that IT has as part of the business, rather than as something that needs to be in alignment with it.
As a case in point, like IT, human resources (HR) and finance are two other assets of the business. A long time ago, companies realized that it made little sense to let each function of the business manage its own finances and human resources. Why should each business group do its own hiring, benefits administration, and office allocation when that role can be centralized for the purpose of efficiency and optimization? So too with finance – why should each role in the business manage its own cash flow, investment, and company-level reporting when it can be centralized for the benefit of the company as a whole.
The key insight here is not one of centralization, since many will claim that IT is also centralized as such. The requirement is one of separation of responsibilities. The HR and finance organizations are not in charge of figuring out how the people and money resources are used. They are simply in charge of managing them for the benefit of the company. It is up to each individual line of business and role to determine how to use the people and money available to it. So too with IT. The IT organization needs to move away from building applications on behalf of the business to providing services that the lines of business can use for their purposes. If we take this perspective of IT as a resource and IT management as management of the IT assets, then we can no longer think of IT project management in the same way.
In the game of IT pick-up-sticks, IT manages and creates the sticks such that when the business picks one up, the model is in place to deal with the iterative changes required. Note the nuance: business picks up the sticks, IT manages them. Say goodbye to discrete IT project management and hello to IT portfolio management.
IT Portfolio Management and The Continuous EA Funding Model
A full discussion of IT portfolio management would require more room than we have here in this ZapFlash, but the core concept is that the IT organization attempts to manage a set of continuously changing resources such that when a new requirement comes in, it doesn’t automatically spawn off a new development project. Rather, the IT organization leverages its growing "catalog" of IT services to meet the continuous needs of the business. Any requirement that is not fulfilled by the existing catalog will require either reconfiguration of existing assets, modification of existing assets, or new asset creation, in that preferable order. But even in the case of new asset creation, the project is the asset creation, not a project aligned with the specific business problem.
The Wikipedia entry on IT Portfolio Management further defines it as such, "the application of systematic management to large classes of items managed by enterprise Information Technology (IT) capabilities… The promise of IT portfolio management is the quantification of previously mysterious IT efforts, enabling measurement and objective evaluation of investment scenarios."
Many of you readers might be scratching your heads right now and wondering, "aren’t we already doing this?" Or perhaps you are saying, "I don’t get how this is different than discrete IT project management." If you are wondering that, then you haven’t yet experienced IT portfolio management, since to do IT portfolio management requires, in most cases, a fundamental change to the lines of IT control and budgeting. To attempt to do IT portfolio management in an environment where the funds are being allocated to projects is a recipe for disaster.
Indeed, changing the method of IT funding is one of the fundamental requirements for a move to a portfolio-centric style of IT management. In an environment where any new business requirement might require changes throughout the organization, it makes no sense to feed IT on a per-project basis. Rather, in an environment of continuous change, the IT organization needs to be provided a continuous, and steady, budget that provides for continuous changes on an iterative model. Each iteration will introduce new assets, versioned assets, and configurations of assets to meet the current set of business requirements. The IT organization then seeks to optimize its portfolio by minimizing the time between iterations, the amount of changes needed in each iteration, the total number of assets under management, and increasing the visibility the rest of the business has of the IT assets under management. In an environment of continuous change, IT needs a continuous funding model to enable to continuous value to the business.
The ZapThink Take
At the highest level of simplicity, all businesses need to manage only four resources in order to maintain success: money, people, technology, and supplies. All of these things are assets, and the organization reflects either the management of these assets or growing the customer base to use or contribute to those assets. IT is no different than finance or human resources. Just as the business doesn’t give HR or finance discrete budgets for specific business requirements, so too will it realize that it needs to treat IT the same way. Successful SOA, as part of the overall move to EA and the realization of composite, loosely-coupled, and potentially reusable IT assets, requires not just addressing the aspects of Service creation and management, but also successfully addressing IT portfolio management.
Document ID: ZAPFLASH-2008612 Document Type: ZapFlash
By: Ronald Schmelzer
Posted: Jun. 12, 2008
One of the most challenging aspects of Enterprise Architecture (EA), and Service-Oriented Architecture (SOA) in particular, is that rather than address a discrete problem or set of problems in the enterprise, it attempts to address a range of interconnected and perplexing issues that have long troubled IT. Specifically, SOA approaches to EA address long-term issues of integration in environments of continued heterogeneity, application development in the face of continuous change, governance, management, and quality in environments of continuous complexity, increasing reuse and reducing redundancy across multiple IT initiatives, and organizational and methodology approaches that favor iteration over monolithic, waterfall-style approaches to development.
While none of these challenges are new, and in fact, many architects have a number of tools, techniques, and approaches at their disposal to address those issues, EA attempts to address them in a holistic manner, providing a consistent approach to use in the face of continued business and technological change. One of the biggest impacts of this holistic approach to IT management is that discrete IT project management is rapidly going by the wayside. This doesn’t signal the death of IT project management, but it does suggest that evolving approaches to EA require changes not just in technology and application development approach, but also changes in the way in which we manage the organization’s overall evolution given that it will become harder to distinguish between development of individual IT projects and advancement of individual IT resources.
The End of the Discrete IT Project
Most corporate IT environments have significant complexity. Even if the set of systems and applications are small in number, their interconnections, customizations, and dependencies quickly evolve into a morass of complexity referred to as the "IT rat’s nest". Into this environment of IT complexity, the business continues to impose their requirements and changes, resulting in the creation of yet more IT resources, interconnections, customizations, and dependencies. This web of complexity quickly becomes so thick that any change to one part of the environment, say a data schema changes, has ripple effects throughout the whole of the organization. Like a game of pick-up-sticks, nothing can move without moving the whole pile.
Yet, most companies still do traditional IT project management in which the requirements are defined and budgets set as if that IT project has no interaction with any of the other IT projects and resources that already exist in the company. In an environment where the web of complexity exists, the notion that you can pick up an "IT stick" without disturbing the rest of the pile makes no sense. One of the prime reasons why many IT projects go over time and budget is because the requirements that seemed simple turn out to be more difficult than anticipated. Some of the difficulty comes from imprecise definition of requirements, but the majority of the challenge comes from realizing how one requirement impacts the system as it already exists. "The Devil’s in the details", as is often said with IT project management, and the Devil is complexity.
Companies that have no plans to do any sort of heterogeneous application development or composition, or who have the time and budget they need to deal with constantly expanding projects in the face of continuously expanding complexity can afford to do discrete IT project management. But for the rest of us, any movement we make to try to bring the organization’s systems together into a predictable, composable, governed, loosely-coupled, and potentially reusable set of assets, or in other words, to apply any real Enterprise Architecture, will require that we stop doing IT project management in a discrete fashion and treat IT as a continuously evolving asset.
Lessons from Human Resources and Finance
Vendors, consultants, and end-users alike over-use and abuse the "Business-IT alignment" refrain without truly understanding what it takes to bring IT into alignment with the rest of the business. Simply facilitating the business requirements to IT implementation generation process is not enough to really turn IT into an asset rather than a cost center. Rather, what’s required is shifting the responsibility for the application of IT to the business and changing the organizational and funding model to reflect the role that IT has as part of the business, rather than as something that needs to be in alignment with it.
As a case in point, like IT, human resources (HR) and finance are two other assets of the business. A long time ago, companies realized that it made little sense to let each function of the business manage its own finances and human resources. Why should each business group do its own hiring, benefits administration, and office allocation when that role can be centralized for the purpose of efficiency and optimization? So too with finance – why should each role in the business manage its own cash flow, investment, and company-level reporting when it can be centralized for the benefit of the company as a whole.
The key insight here is not one of centralization, since many will claim that IT is also centralized as such. The requirement is one of separation of responsibilities. The HR and finance organizations are not in charge of figuring out how the people and money resources are used. They are simply in charge of managing them for the benefit of the company. It is up to each individual line of business and role to determine how to use the people and money available to it. So too with IT. The IT organization needs to move away from building applications on behalf of the business to providing services that the lines of business can use for their purposes. If we take this perspective of IT as a resource and IT management as management of the IT assets, then we can no longer think of IT project management in the same way.
In the game of IT pick-up-sticks, IT manages and creates the sticks such that when the business picks one up, the model is in place to deal with the iterative changes required. Note the nuance: business picks up the sticks, IT manages them. Say goodbye to discrete IT project management and hello to IT portfolio management.
IT Portfolio Management and The Continuous EA Funding Model
A full discussion of IT portfolio management would require more room than we have here in this ZapFlash, but the core concept is that the IT organization attempts to manage a set of continuously changing resources such that when a new requirement comes in, it doesn’t automatically spawn off a new development project. Rather, the IT organization leverages its growing "catalog" of IT services to meet the continuous needs of the business. Any requirement that is not fulfilled by the existing catalog will require either reconfiguration of existing assets, modification of existing assets, or new asset creation, in that preferable order. But even in the case of new asset creation, the project is the asset creation, not a project aligned with the specific business problem.
The Wikipedia entry on IT Portfolio Management further defines it as such, "the application of systematic management to large classes of items managed by enterprise Information Technology (IT) capabilities… The promise of IT portfolio management is the quantification of previously mysterious IT efforts, enabling measurement and objective evaluation of investment scenarios."
Many of you readers might be scratching your heads right now and wondering, "aren’t we already doing this?" Or perhaps you are saying, "I don’t get how this is different than discrete IT project management." If you are wondering that, then you haven’t yet experienced IT portfolio management, since to do IT portfolio management requires, in most cases, a fundamental change to the lines of IT control and budgeting. To attempt to do IT portfolio management in an environment where the funds are being allocated to projects is a recipe for disaster.
Indeed, changing the method of IT funding is one of the fundamental requirements for a move to a portfolio-centric style of IT management. In an environment where any new business requirement might require changes throughout the organization, it makes no sense to feed IT on a per-project basis. Rather, in an environment of continuous change, the IT organization needs to be provided a continuous, and steady, budget that provides for continuous changes on an iterative model. Each iteration will introduce new assets, versioned assets, and configurations of assets to meet the current set of business requirements. The IT organization then seeks to optimize its portfolio by minimizing the time between iterations, the amount of changes needed in each iteration, the total number of assets under management, and increasing the visibility the rest of the business has of the IT assets under management. In an environment of continuous change, IT needs a continuous funding model to enable to continuous value to the business.
The ZapThink Take
At the highest level of simplicity, all businesses need to manage only four resources in order to maintain success: money, people, technology, and supplies. All of these things are assets, and the organization reflects either the management of these assets or growing the customer base to use or contribute to those assets. IT is no different than finance or human resources. Just as the business doesn’t give HR or finance discrete budgets for specific business requirements, so too will it realize that it needs to treat IT the same way. Successful SOA, as part of the overall move to EA and the realization of composite, loosely-coupled, and potentially reusable IT assets, requires not just addressing the aspects of Service creation and management, but also successfully addressing IT portfolio management.
Tuesday, June 10, 2008
A nice case study on experiences adoption TFS in a cross platform development team using Teamprise for Java developers
A recently published case study with Thomson Reuters on their experiences adoption TFS in a cross platform development team using Teamprise for their Java developers. It's a great testament to how the combination of these two products can work together to create a comprehensive ALM solution for a significant development team. I frequently get asked about how well TFS + Teamprise can meet the needs of a Java development team.
http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=4000002078
http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=4000002078
Friday, May 30, 2008
Microsoft Advisory: Changes to Daylight Saving Time in Morocco and Pakistan on June 1, 2008
Link:
http://blogs.msdn.com/nickmac/archive/2008/05/30/advisory-changes-to-daylight-saving-time-in-morocco-and-pakistan-on-june-1-2008.aspx
Advisory: Changes to Daylight Saving Time in Morocco and Pakistan on June 1, 2008
Daylight Saving Time changes in Morocco and Pakistan (revised May 23, 2008)
Microsoft has learned of a change to the observance of Daylight Saving Time (DST, aka regionally as Summer Time) in Morocco and Pakistan that could impact customers using local time zones. We have news that Morocco will switch from GMT to GMT+1:00 beginning on June 1, 2008, and that the Pakistan Government will change from GMT +5:00 to GMT +6:00 June 1, 2008, at 12 midnight (local time). These changes may impact customers and partners in the regions who use local time zones, including entities engaged in business in or with the region.
Unfortunately, due to the short notice provided for these late breaking changes, we do not expect that product groups will provide updates incorporating these changes. The Windows organization plans to include these updates in the next release of the 2008 Cumulative Time Zone Update for Windows, scheduled to release in July/August 2008.
For manual remediation of the Microsoft Windows XP operating systems in mainstream support, Microsoft will provide an updating to the following DST and time zone manual update article with the changes for Morocco and Pakistan:
How to configure daylight saving time for Microsoft Windows operating systems
http://support.microsoft.com/kb/914387
We will publish additional information and links here as available. For general information, please visit http://www.microsoft.com/time.
We've also updated the information in the KB to indicate that Iraq no longer observes DST.
Nick.
http://blogs.msdn.com/nickmac/archive/2008/05/30/advisory-changes-to-daylight-saving-time-in-morocco-and-pakistan-on-june-1-2008.aspx
Advisory: Changes to Daylight Saving Time in Morocco and Pakistan on June 1, 2008
Daylight Saving Time changes in Morocco and Pakistan (revised May 23, 2008)
Microsoft has learned of a change to the observance of Daylight Saving Time (DST, aka regionally as Summer Time) in Morocco and Pakistan that could impact customers using local time zones. We have news that Morocco will switch from GMT to GMT+1:00 beginning on June 1, 2008, and that the Pakistan Government will change from GMT +5:00 to GMT +6:00 June 1, 2008, at 12 midnight (local time). These changes may impact customers and partners in the regions who use local time zones, including entities engaged in business in or with the region.
Unfortunately, due to the short notice provided for these late breaking changes, we do not expect that product groups will provide updates incorporating these changes. The Windows organization plans to include these updates in the next release of the 2008 Cumulative Time Zone Update for Windows, scheduled to release in July/August 2008.
For manual remediation of the Microsoft Windows XP operating systems in mainstream support, Microsoft will provide an updating to the following DST and time zone manual update article with the changes for Morocco and Pakistan:
How to configure daylight saving time for Microsoft Windows operating systems
http://support.microsoft.com/kb/914387
We will publish additional information and links here as available. For general information, please visit http://www.microsoft.com/time.
We've also updated the information in the KB to indicate that Iraq no longer observes DST.
Nick.
Thursday, May 29, 2008
Team System Widgets
Team System Widgets (a very useful resource)
This is a list of various Visual Studio Team System add-ins, add-ons, widgets, and extensibility solutions.
http://widgets.accentient.com/default.aspx
Thursday, May 15, 2008
A nice white paper on Requirement Managemet with VSTS 2008
This white paper outlines how to use Visual Studio Team System for successful requirements management using Visual Studio Team System 2005 or Visual Studio Team System 2008. In addition, you can use this paper to learn about some of the challenges that Microsoft intends to address in the next release: Visual Studio Team System code name "Rosario".
Requirements Management with Visual Studio Team System White Paper
Google conquered Earth so Microsoft went for space !!
Check out this link for Microsoft Worldwide Telescope, its space exploration from ur desktop, Microsoft does innovate stuff :)
http://www.worldwidetelescope.org/experienceIt/ExperienceIt.aspx?exp=true
http://www.microsoft.com/presspass/press/2008/may08/05-12WWTPR.mspx
Imran Khawar Bodla
Microsoft Professional Partner
http://www.worldwidetelescope.org/experienceIt/ExperienceIt.aspx?exp=true
http://www.microsoft.com/presspass/press/2008/may08/05-12WWTPR.mspx
Imran Khawar Bodla
Microsoft Professional Partner
Monday, May 05, 2008
Windows SharePoint Services 3.0 Overview
Introduction
Microsoft Windows SharePoint Services 3.0 is a versatile technology that organizations and business units of all sizes can use to increase the efficiency of business processes and improve team productivity. With tools for collaboration that help people stay connected across organizational and geographic boundaries, Windows SharePoint Services gives people access to information they need.
Built on Microsoft Windows Server 2003, Windows SharePoint Services also provides a foundation platform for building Web-based business applications that can flex and scale easily to meet the changing and growing needs of your business. Robust administrative controls for managing storage and Web infrastructure give IT departments a cost-effective way to implement and manage a high-performance collaboration environment. With a familiar, Web-based interface and close integration with everyday tools including the Microsoft Office system, Windows SharePoint Services is easy to use and can be deployed rapidly.
Collaborate Easily and Effectively
Windows SharePoint Services helps teams stay connected and productive by providing easy access to the people, documents, and information they need to make more informed decisions and get the job done. Enhancements in Windows SharePoint Services 3.0 make it easier than ever to share documents, track tasks, use e-mail efficiently and effectively, and share ideas and information.
Provide a single workspace for teams to coordinate schedules, organize documents, and participate in discussions—within the organization and over the extranet.
Easily author and manage documents, and help to ensure their integrity with enhanced features including the option to require document checkout before editing, the ability to view past revisions and restore to previous versions, and the ability to set document-specific security.
Help people and teams stay on task with a variety of communication features that let users know when actions are required or important changes are made to existing information or documentation, including announcements, sophisticated alerts, surveys, and discussion boards.
Provide creative forums for brainstorming ideas, building knowledge bases, or simply gathering information in an easy-to-edit format with new templates for implementing blogs (also known as weblogs) and wikis (Web sites that can be quickly edited by team members—no special technical knowledge required).
Stay productive while mobile with enhanced support for offline synchronization through Microsoft Office Outlook 2007 that users can use to manage document libraries, lists, calendars, contacts, tasks, and discussion boards even offline, and to synchronize changes when reconnected to the network.
Get Started Quickly
As a built-in component of Windows Server 2003, Windows SharePoint Services makes it easy for IT departments to implement a dependable, scalable collaboration infrastructure with minimal administrative time and effort. Close integration of Windows SharePoint Services with familiar tools for authoring, publishing, organizing, and finding information, including the Microsoft Office system, helps users get up to speed quickly.
Simplify the creation and navigation of workspaces with the improved user interface and site creation tools in Windows SharePoint Services 3.0 that provide easy-to-use templates, professional-looking site themes, and the ability to rearrange site navigation from within the browser.
Make it easy for users to get up to speed quickly by providing integration with familiar productivity tools such as those found in the Microsoft Office system—users can create workspaces, post and edit documents, and view and update calendars on SharePoint sites, all while working within Microsoft Office system files and programs.
Track work and tasks more easily with enhanced integration with Office Outlook 2007 that helps users organize calendars, tasks, contact lists, discussion boards, and meetings.
Customize workspaces with new application templates that provide custom scenarios for building workflows on the Windows SharePoint Services platform that address specific business processes or sets of tasks.
Implement a collaboration environment with minimal administrative time and effort, and with the flexibility to change deployment settings.
Deploy a Manageable Infrastructure
Deployment of Windows SharePoint Services 3.0 increases control over and enhances security of your organization’s data and information resources. Reduce the dependency of business units on your company’s IT department for site provisioning, implementation, backup, and support. Whether you’re a contributor to a team site, a site owner, or a server administrator, Windows SharePoint Services 3.0 provides better administrative controls for managing content, users, and sites so that individuals and teams can operate more efficiently and effectively.
Increase the security of business information with enhanced administrative controls that decrease cost and complexity associated with site provisioning, management, support, operations, and backup and restore.
Give IT better control over your organization’s infrastructure with new and improved services for controlling access to information and setting policies for site creation that enable security to be set as deep down as the item level.
Empower site managers and teams without compromising security by enabling them to initiate and control their own self-service workspaces and tasks, and manage the participation and access of others—all within parameters set by IT.
Provide a more robust document storage environment with document storage, recycle bin item retrieval, and version-control features built in to team workspaces.
Easily manage and configure Windows SharePoint Services by using a Web browser or command-line utilities, and enable a variety of custom and third-party administration solutions using the Microsoft .NET Framework.
Provide a Foundation for Web-Based Applications
With Windows SharePoint Services 3.0, IT professionals can tailor or extend the Windows SharePoint Services foundation to create new, efficient, Web-based tools and services specific to the organization, department, business process, or industry vertical. Through a highly customizable and extensible platform, companies can tie these new tools and services to existing line-of-business applications, capitalizing on existing IT investments and valuable information stored in back-end systems.
Manage business documents more easily with enhanced document library support and a common repository for document storage.
Use the Windows SharePoint Services platform to build rich, flexible, and scalable Web-based applications and Internet sites specific to the needs of your organization.
Take advantage of integration with Microsoft Office SharePoint Server 2007 that expands the platform services and common framework for document management exposed by Windows SharePoint Services to offer enterprise-wide functionality for records management, search, workflows, portals, personalized sites, and more.
Use Microsoft Office SharePoint Designer 2007 to quickly and easily customize SharePoint sites and build reporting tools and applications tailored to specific tasks without writing or deploying new code.
Microsoft Windows SharePoint Services 3.0 is a versatile technology that organizations and business units of all sizes can use to increase the efficiency of business processes and improve team productivity. With tools for collaboration that help people stay connected across organizational and geographic boundaries, Windows SharePoint Services gives people access to information they need.
Built on Microsoft Windows Server 2003, Windows SharePoint Services also provides a foundation platform for building Web-based business applications that can flex and scale easily to meet the changing and growing needs of your business. Robust administrative controls for managing storage and Web infrastructure give IT departments a cost-effective way to implement and manage a high-performance collaboration environment. With a familiar, Web-based interface and close integration with everyday tools including the Microsoft Office system, Windows SharePoint Services is easy to use and can be deployed rapidly.
Collaborate Easily and Effectively
Windows SharePoint Services helps teams stay connected and productive by providing easy access to the people, documents, and information they need to make more informed decisions and get the job done. Enhancements in Windows SharePoint Services 3.0 make it easier than ever to share documents, track tasks, use e-mail efficiently and effectively, and share ideas and information.
Provide a single workspace for teams to coordinate schedules, organize documents, and participate in discussions—within the organization and over the extranet.
Easily author and manage documents, and help to ensure their integrity with enhanced features including the option to require document checkout before editing, the ability to view past revisions and restore to previous versions, and the ability to set document-specific security.
Help people and teams stay on task with a variety of communication features that let users know when actions are required or important changes are made to existing information or documentation, including announcements, sophisticated alerts, surveys, and discussion boards.
Provide creative forums for brainstorming ideas, building knowledge bases, or simply gathering information in an easy-to-edit format with new templates for implementing blogs (also known as weblogs) and wikis (Web sites that can be quickly edited by team members—no special technical knowledge required).
Stay productive while mobile with enhanced support for offline synchronization through Microsoft Office Outlook 2007 that users can use to manage document libraries, lists, calendars, contacts, tasks, and discussion boards even offline, and to synchronize changes when reconnected to the network.
Get Started Quickly
As a built-in component of Windows Server 2003, Windows SharePoint Services makes it easy for IT departments to implement a dependable, scalable collaboration infrastructure with minimal administrative time and effort. Close integration of Windows SharePoint Services with familiar tools for authoring, publishing, organizing, and finding information, including the Microsoft Office system, helps users get up to speed quickly.
Simplify the creation and navigation of workspaces with the improved user interface and site creation tools in Windows SharePoint Services 3.0 that provide easy-to-use templates, professional-looking site themes, and the ability to rearrange site navigation from within the browser.
Make it easy for users to get up to speed quickly by providing integration with familiar productivity tools such as those found in the Microsoft Office system—users can create workspaces, post and edit documents, and view and update calendars on SharePoint sites, all while working within Microsoft Office system files and programs.
Track work and tasks more easily with enhanced integration with Office Outlook 2007 that helps users organize calendars, tasks, contact lists, discussion boards, and meetings.
Customize workspaces with new application templates that provide custom scenarios for building workflows on the Windows SharePoint Services platform that address specific business processes or sets of tasks.
Implement a collaboration environment with minimal administrative time and effort, and with the flexibility to change deployment settings.
Deploy a Manageable Infrastructure
Deployment of Windows SharePoint Services 3.0 increases control over and enhances security of your organization’s data and information resources. Reduce the dependency of business units on your company’s IT department for site provisioning, implementation, backup, and support. Whether you’re a contributor to a team site, a site owner, or a server administrator, Windows SharePoint Services 3.0 provides better administrative controls for managing content, users, and sites so that individuals and teams can operate more efficiently and effectively.
Increase the security of business information with enhanced administrative controls that decrease cost and complexity associated with site provisioning, management, support, operations, and backup and restore.
Give IT better control over your organization’s infrastructure with new and improved services for controlling access to information and setting policies for site creation that enable security to be set as deep down as the item level.
Empower site managers and teams without compromising security by enabling them to initiate and control their own self-service workspaces and tasks, and manage the participation and access of others—all within parameters set by IT.
Provide a more robust document storage environment with document storage, recycle bin item retrieval, and version-control features built in to team workspaces.
Easily manage and configure Windows SharePoint Services by using a Web browser or command-line utilities, and enable a variety of custom and third-party administration solutions using the Microsoft .NET Framework.
Provide a Foundation for Web-Based Applications
With Windows SharePoint Services 3.0, IT professionals can tailor or extend the Windows SharePoint Services foundation to create new, efficient, Web-based tools and services specific to the organization, department, business process, or industry vertical. Through a highly customizable and extensible platform, companies can tie these new tools and services to existing line-of-business applications, capitalizing on existing IT investments and valuable information stored in back-end systems.
Manage business documents more easily with enhanced document library support and a common repository for document storage.
Use the Windows SharePoint Services platform to build rich, flexible, and scalable Web-based applications and Internet sites specific to the needs of your organization.
Take advantage of integration with Microsoft Office SharePoint Server 2007 that expands the platform services and common framework for document management exposed by Windows SharePoint Services to offer enterprise-wide functionality for records management, search, workflows, portals, personalized sites, and more.
Use Microsoft Office SharePoint Designer 2007 to quickly and easily customize SharePoint sites and build reporting tools and applications tailored to specific tasks without writing or deploying new code.
Wednesday, December 05, 2007
OBA Training Event at Digital Spinners Islamabad
Under Microsoft Professional Partner Program, a training event at Digital Spinners Islamabad on Office Business Application(OBA) was arranged by Mr. Wasif Raza Mirza(Microsoft Professional Partner) CTO, Digital Spinners on 1st December 2007, Mr Imran Khawar speak on OBA related technologies where professionals can meet the current and future challenges.
-- Imran Khawar Bodla
-- Imran Khawar Bodla
Wednesday, November 28, 2007
Team Development with Team Foundation Server Guide
Microsoft just released the final version of the “Team Development with Team Foundation Server” Guide. This guide shows you how to get the most out of Team Foundation Server to help improve the effectiveness of your team-based software development. Whether you are already using Team Foundation Server or adopting from scratch, you’ll find guidance and insights you can tailor for your specific scenarios. It's a collaborative effort between patterns & practices, Team System team members, and industry experts.
http://www.codeplex.com/TFSGuide
Imran Khawar Bodla
http://www.codeplex.com/TFSGuide
Imran Khawar Bodla
Sunday, May 06, 2007
Share Point Licencing
During my trainings so many people ask me about the licencing of Share point , so here is the official reference from Microsoft
http://office.microsoft.com/en-us/sharepointserver/FX101865111033.aspx
http://office.microsoft.com/en-us/sharepointserver/FX101865111033.aspx
Virtual Labs
if you want to get your hands dirty on Sharepoint 2007 or other microsoft technogies and you don't have environment readily available, try Virtual Labs
http://www.microsoft.com/technet/traincert/virtuallab/office.mspx
http://www.microsoft.com/technet/traincert/virtuallab/office.mspx
Share Point 2007
MS Office SPS 2007 merges functionality of Content Management Server (MCMS) 2002 and Microsoft Office SharePoint Portal Server 2003 with new functionality to create one integrated set of technologies built on Microsoft Windows SharePoint Services 3.0.
http://msdn2.microsoft.com/library/aa830819.aspx
http://msdn2.microsoft.com/library/aa830819.aspx
Friday, May 04, 2007
SharePoint Server 2007 - Key Performance Indicators (KPIs)
Key Performance Indicators (KPIs)
A Key Performance Indicator (KPI) is a visual signal that tells us the amount of progress made towards a goal. In this article lets see how to create and display KPIs by using Microsoft Office SharePoint Server 2007 KPI list.
How-ToKPIs are valuable resources to evaluate progress against measurable goals. To create and publish KPIs, there is a four step procedure.
Create a KPI list Add the KPI to the list Add a Web Part to a Web page Link the KPI list to the Web Part.
First of all we need to choose a KPI Type:
KPI typesUsing data in SharePoint listsWhen SharePoint lists contain items that you can count, items that are part of a workflow, or items that contain dates, you can use a KPI to track how long the issues or tasks have been open, how many are open, and what percentage of a task is complete.
Using data in Microsoft Office Excel workbooksYou can set up a KPI in an Excel workbook and link to the KPI from Office SharePoint Server 2007. As the data in the workbook changes, the KPI is automatically updated.
Using data from Microsoft SQL Server 2005 Analysis ServicesOffice SharePoint Server 2007 can use KPIs from Analysis Services, a component of Microsoft SQL Server 2005. A systems administrator or database analyst usually sets up these KPIs and registers the data connection with Office SharePoint Server. Then, anyone with the appropriate permissions can access the database and link to the Analysis Services KPIs.
Using manually entered informationIn situations where there is no formal system set up or you have a one-time project to track, you can use this KPI and enter the criteria manually. This KPI is useful for displaying information that is communicated in e-mail or some other nonstructured system.
Create a KPI listYou can create KPI lists in the Reports Library of the Reports Center in a team or organization site, so that other people easily can find them.
1. In the site where you want to create the KPI list, on the default page of the Report Center, click Site Actions, and then select View All Site Content. Under the All Site Content heading, click Create.
2. On the Create page, under Custom Lists, click KPI List.
3. Type a name and an optional description for the KPI list.
4. Click OK.
You now have a KPI list to which you can add one or more KPI types.
Add a KPI to the KPI list1. On the KPI list toolbar, click the arrow next to New.
2. Select “Indicator using data in SharePoint list” KPI type.
3. On the New Indicator page, do the following:a) In the Name and Description boxes, type a name and optional description for the indicator.b) In the Comments box, type text to help people who are viewing the KPI understand what it represents.c) Under SharePoint List and View, in the List URL box, enter the URL of the list or library.d) In View, select the view that contains the items you want to use in the KPI.e) Under Value Calculation, select one of the following ways to calculate the goal of the KPI: Number of list items: A count of the total number of items in the list. Percentage of list items: A calculation that compares the value of a content type within a column or up to five columns in the list. Calculation using all list items in the view: A computation of Total, Average, Maximum, or Minimum of a numerical column in the list. Note The Calucaltion using all list items in the view option is only available if your list includes a numerical field.
4. In the Status Icon section, under Status Icon Rules, in the Better values are list, select higher or lower to indicate which range of numbers will be green.
5. Type the values for the status indicators in the boxes. For example, to track the minimum percentage complete for a set of tasks, you can set the green indicator at the goal value and the warning value to be one less than the goal value. In that case, if you want to see when the minimum percentage complete drops below 25 percent, you set the green indicator to 25 and the yellow indicator to 24.
After you add all of the KPIs that you want to the KPI list, you can publish them on a Web page by using one of two KPI Web Parts.
Publish the KPI on a Web pageAfter you add one or more KPI types to the KPI list, you can display the KPI list on My Site, a team site, or any other SharePoint page. In addition, the KPI list is available for use by anyone in your organization who has permissions to access it. You can use one or all of the KPIs that appear on the list. To display the KPIs, you edit the Web page where you want to display the KPI list and add a KPI Web Part. To display the entire KPI list, use the KPI List Web Part. To show only one of the KPIs from the list, use the KPI Details Web Part.
Add a Web Part to a page1. On the page where you want to add the KPI, click Site Actions, and then select Edit Page.
2. In the zone in which you want to add the KPI, click Add a Web Part.
3. In the Add Web Parts dialog box, in the All Web Parts section, under Dashboard, do one of the following. To insert the entire KPI list, select Key Performance Indicators. To choose one KPI from the KPI list, select KPI Details.
4. Click Add.
Link the KPI list to the Web Part1. In the Web Part, click Open the tool pane.
2. In the tool pane, under Indicator List, navigate to and double-click the KPI list that you created in the previous set of procedures. The list may be in the Report Center of the site.3. Select one of the KPIs in the list. (If you selected the KPI List, the entire list is displayed.)
4. Click OK.
A Key Performance Indicator (KPI) is a visual signal that tells us the amount of progress made towards a goal. In this article lets see how to create and display KPIs by using Microsoft Office SharePoint Server 2007 KPI list.
How-ToKPIs are valuable resources to evaluate progress against measurable goals. To create and publish KPIs, there is a four step procedure.
Create a KPI list Add the KPI to the list Add a Web Part to a Web page Link the KPI list to the Web Part.
First of all we need to choose a KPI Type:
KPI typesUsing data in SharePoint listsWhen SharePoint lists contain items that you can count, items that are part of a workflow, or items that contain dates, you can use a KPI to track how long the issues or tasks have been open, how many are open, and what percentage of a task is complete.
Using data in Microsoft Office Excel workbooksYou can set up a KPI in an Excel workbook and link to the KPI from Office SharePoint Server 2007. As the data in the workbook changes, the KPI is automatically updated.
Using data from Microsoft SQL Server 2005 Analysis ServicesOffice SharePoint Server 2007 can use KPIs from Analysis Services, a component of Microsoft SQL Server 2005. A systems administrator or database analyst usually sets up these KPIs and registers the data connection with Office SharePoint Server. Then, anyone with the appropriate permissions can access the database and link to the Analysis Services KPIs.
Using manually entered informationIn situations where there is no formal system set up or you have a one-time project to track, you can use this KPI and enter the criteria manually. This KPI is useful for displaying information that is communicated in e-mail or some other nonstructured system.
Create a KPI listYou can create KPI lists in the Reports Library of the Reports Center in a team or organization site, so that other people easily can find them.
1. In the site where you want to create the KPI list, on the default page of the Report Center, click Site Actions, and then select View All Site Content. Under the All Site Content heading, click Create.
2. On the Create page, under Custom Lists, click KPI List.
3. Type a name and an optional description for the KPI list.
4. Click OK.
You now have a KPI list to which you can add one or more KPI types.
Add a KPI to the KPI list1. On the KPI list toolbar, click the arrow next to New.
2. Select “Indicator using data in SharePoint list” KPI type.
3. On the New Indicator page, do the following:a) In the Name and Description boxes, type a name and optional description for the indicator.b) In the Comments box, type text to help people who are viewing the KPI understand what it represents.c) Under SharePoint List and View, in the List URL box, enter the URL of the list or library.d) In View, select the view that contains the items you want to use in the KPI.e) Under Value Calculation, select one of the following ways to calculate the goal of the KPI: Number of list items: A count of the total number of items in the list. Percentage of list items: A calculation that compares the value of a content type within a column or up to five columns in the list. Calculation using all list items in the view: A computation of Total, Average, Maximum, or Minimum of a numerical column in the list. Note The Calucaltion using all list items in the view option is only available if your list includes a numerical field.
4. In the Status Icon section, under Status Icon Rules, in the Better values are list, select higher or lower to indicate which range of numbers will be green.
5. Type the values for the status indicators in the boxes. For example, to track the minimum percentage complete for a set of tasks, you can set the green indicator at the goal value and the warning value to be one less than the goal value. In that case, if you want to see when the minimum percentage complete drops below 25 percent, you set the green indicator to 25 and the yellow indicator to 24.
After you add all of the KPIs that you want to the KPI list, you can publish them on a Web page by using one of two KPI Web Parts.
Publish the KPI on a Web pageAfter you add one or more KPI types to the KPI list, you can display the KPI list on My Site, a team site, or any other SharePoint page. In addition, the KPI list is available for use by anyone in your organization who has permissions to access it. You can use one or all of the KPIs that appear on the list. To display the KPIs, you edit the Web page where you want to display the KPI list and add a KPI Web Part. To display the entire KPI list, use the KPI List Web Part. To show only one of the KPIs from the list, use the KPI Details Web Part.
Add a Web Part to a page1. On the page where you want to add the KPI, click Site Actions, and then select Edit Page.
2. In the zone in which you want to add the KPI, click Add a Web Part.
3. In the Add Web Parts dialog box, in the All Web Parts section, under Dashboard, do one of the following. To insert the entire KPI list, select Key Performance Indicators. To choose one KPI from the KPI list, select KPI Details.
4. Click Add.
Link the KPI list to the Web Part1. In the Web Part, click Open the tool pane.
2. In the tool pane, under Indicator List, navigate to and double-click the KPI list that you created in the previous set of procedures. The list may be in the Report Center of the site.3. Select one of the KPIs in the list. (If you selected the KPI List, the entire list is displayed.)
4. Click OK.
Thursday, May 18, 2006
Windows Share Point Services
A good introductory presentation by Microsoft can @ WSS is available @
http://www.microsoft.com/windowsserver2003/technologies/sharepoint/wss_overview.html
It demonstrates the features of WSS step by step.
http://www.microsoft.com/windowsserver2003/technologies/sharepoint/wss_overview.html
It demonstrates the features of WSS step by step.
Tuesday, May 16, 2006
Building an ASP.NET Shopping Cart Using DataTables
http://www.sitepoint.com/article/net-shopping-cart-datatables
Quick development link of shopping cart implementation.
Quick development link of shopping cart implementation.
Monday, May 15, 2006
Creating a Simple Site in Portal Server
SPWeb mySite = SPControl.GetContextWeb(Context);SPWebCollection subSites = mySite.Webs;string currentTemplate = mySite.WebTemplate;
string siteUrl = TextBox1.Text.ToString(); //you can use hard coded path herestring siteTitle = TextBox2.Text.ToString(); //you can use hard coded title for testing purposesstring
siteDescription = TextBox3.Text.ToString(); //use hard coded description for testing
subSites.Add(siteUrl, siteTitle, siteDescription, 1033, currentTemplate, true, false);
From SPS 2003 SDK
string siteUrl = TextBox1.Text.ToString(); //you can use hard coded path herestring siteTitle = TextBox2.Text.ToString(); //you can use hard coded title for testing purposesstring
siteDescription = TextBox3.Text.ToString(); //use hard coded description for testing
subSites.Add(siteUrl, siteTitle, siteDescription, 1033, currentTemplate, true, false);
From SPS 2003 SDK
Subscribe to:
Posts (Atom)