Microsoft’s own social networking platform is ready! It is especially for India!

Visit and Joint now! - http://wlplanet.com/

A quick answer will be “to make development environments more productive, consistent and standardized”. As an addendum, it accelerates project cycle times, reduce costs.

It is important that companies must update their applications for compatibility with rapid evaluation of  technologies such as mobile devices, software as a service etc. Customers must be happy even after their database grow and the application complexity increases. Current trend is to follow Agile Methodology which forces the stack holders to use iterations for development and reusability of code can save much time.

Some companies commented that they were able to improve productivity of developer up to 40% by reusing assets from Patterns and Practices.

It is also possible to reduce the project cycle times by using pre-built application blocks in Patterns & Practices rather than building the code from scratch.

Some companies commented they were able to shorten project cycle times up to  25% by using pre-built components of Enterprise Library

Here comes the role of Microsoft Patterns and Practices. This gives guidance to to companies to do

• design
• develop
• deploy

using Microsoft platform effectively and rapidly.

If you plan to use Patterns & Practices for your company, you will be spending less time for development it may be even less time than your requirement analysis time.

Microsoft provide:

• A group of Patterns & Practices tools are freely available and
• The Source Code of these tools as also available for free so that the company can alter and use if they need.

The Microsoft Patterns & Practices supports Web, Windows, Mobile Devices etc. These are the forms of support we can avail:

• Enterprise Library Application Blocks – Reusable library for:
• Data Access
• Caching
• Cryptography
• Exception Handling
• Logging, Security
• Policy Injection and
• Validation
• Software Factory – Helps architects and developers to create instances of specify types of applications
• Guides – Architecture and Design guidelines
• Reference Implementations – Sample applications

References: 1) Guidebook Microsoft Patterns and Practices 2) Internet

Check this link from Microsoft Patterns & Practices - http://msdn.microsoft.com/en-us/library/ms998208.aspx

You must read the TFS Guide -http://www.codeplex.com/TFSGuide if you try to be a .NET Architect. (ebook available for download)

Global hooks are not supported in the .NET Framework

Except for the WH_KEYBOARD_LL low-level hook and the WH_MOUSE_LL low-level hook, you cannot implement global hooks in the Microsoft .NET Framework. To install a global hook, a hook must have a native DLL export to inject itself in another process that requires a valid, consistent function to call into. This behavior requires a DLL export. The .NET Framework does not support DLL exports. Managed code has no concept of a consistent value for a function pointer because these function pointers are proxies that are built dynamically.

Low-level hook procedures are called on the thread that installed the hook. Low-level hooks do not require that the hook procedure be implemented in a DLL.

Read more: http://support.microsoft.com/kb/318804

Here are some photos and videos took while TechEd @ Technopark, Trivandrum.

Photos - http://www.flickr.com/photos/visualanand/

Videos - http://www.youtube.com/techedtvm

Source

I just posted my new CodeProject article Flex Communication with ASP.NET WebService. This article demonstrates how to communicate our ordinary ASP.NET WebService with Adobe’s Flex.

Read here: http://www.codeproject.com/KB/aspnet/FlexASPWebService.aspx

Maximum number of users:

So far, testing in this area has yet to reveal any new recommended limits to the number of members in a group or any other linked multivalued attribute. Production environments have been reported to exceed 4 million members, and Microsoft scalability testing reached 500 million members.

http://technet.microsoft.com/en-us/library/cc756101(WS.10).aspx

Above link explains these useful details:

• Maximum Number of Objects
• Maximum Number of Security Identifiers
• Group Memberships for Security Principals
• FQDN Length Limitations
• File Name Length Limitations
• Additional Name Length Limitations
• Maximum Number of GPOs Applied
• Trust Limitations
• Maximum Number of Accounts per LDAP Transaction
• Recommended Maximum Number of Users in a Group
• Recommended Maximum Number of Domains in a Forest
• Recommended Maximum Number of Domain Controllers in a Domain
• Recommended Maximum Kerberos Settings

When you pass getdate() function as a parameter directly to a stored procedure, you will get an error: Incorrect syntax near ‘)’.

EXEC sp_GetProject GETDATE()
 
Error:
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near ')'.

To avoid this, you will need to create a variable and pass it to the stored procedure. Like this:

DECLARE @dt DATETIME;
SET @dt=GETDATE();
 
EXEC sp_GetProject @dt

Here, I used a basic WebService created with ASP.NET. Below is a basic hello world functionality we get when creating a new WebService with Visual Studio.

using System.Web.Services;
 
[WebService(Namespace = "http://tempuri.org/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
 
public class Service : System.Web.Services.WebService
{
    public Service () {
 
    }
 
    [WebMethod]
    public string HelloWorld() {
        return "Hello World - This is Praveen";
    }
}

Below is the basic mxml code which will show you text from WebService:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
 
<mx:Script>
	<![CDATA[
		import mx.controls.Alert;
		import mx.rpc.events.FaultEvent;
		import mx.rpc.events.ResultEvent;
		private function result(event:ResultEvent):void {
			Alert.show(event.result.toString());
		}
		private function fault(event:FaultEvent):void {
			Alert.show(event.toString());
		}
		private function invokemethod(event:MouseEvent):void {
			ws.HelloWorld();
		}
	]]>
</mx:Script>
 
<mx:WebService id="ws" wsdl="http://localhost/FlexWSTest/Service.asmx?WSDL">
<mx:operation 
	name="HelloWorld" 
	resultFormat="object"
	result="result(event)"
	fault="fault(event)"
	 />
</mx:WebService>		
	<mx:Button x="236" y="177" label="Button" click="invokemethod(event)" />
</mx:Application>

My new article Flex HTTPService with ASP.NET posted to CodeProject.

Read it now