Here are SEVEN wonderful projects on MOSS 2007

Hi Dudes,

If you are a starter in Microsoft Office Share Server, then here is the cool link on how to start a project from scratch.

http://download.microsoft.com/download/0/2/f/02f0f661-88e1-43c2-b523-88d2e9e6802f/7%20Development%20Projects%20with%20the%202007%20Microsoft%20Office%20System%20and%20Windows%20SharePoint%20Services%202007.pdf

MOSS 2007 Configuration Techniques

Dudes,
Here is a cool link on how to configure the different features in SharePoint Server 2007 for our needs.
Check out the link.

http://clintcherry.spaces.live.com/Blog/cns!AEC0DCBC460E45B9!535.entry

One of the best VISAUL I have seen. Might be you have seen this. But be it practical. very good

Here is the Lead India advertisement on you tube. A very nice and must watch video.
Be an Indian and do as an Indian to make our India to a Great country.

Here is the link to update you in Blood Groups..

Hi Pals,
Please register to this site and be a part of SAVING LIVES.

++++ Donate Blood and Save Lives++++

A Beautiful Melody Dedicated to MUSIC LOVERS..

User Controls Vs Custom Controls, Looks similar. But here is the difference.

Hi,
Generally the programmer feels that the custom controls and user controls are similar in nature.
(Almost not exactly.)

But there are lot of differences between these two in nature and in execution.
Here are some cool links to have a look at them.

http://support.microsoft.com/kb/893667
http://steveorr.net/faq/UserCustom.aspx
http://www.oreilly.com/catalog/progaspdotnet/chapter/ch14.html

A Great and nice article about our ROLE MODEL

The man who went from being a small town boy in Tamil Nadu, to pioneering the science of Aeronautical Engineering to leading a country of millions into a future free of poverty and misery. The man who began his term as the president of India on July 25th, 2002, shall now move over to make way for another who, we hope, will lead India on in a manner befitting the standards set by A.P.J Abdul Kalam. Here we pay our tributes to the President of the Masses.

Typical Page life cycle in ASP.Net 2.0

ASP.NET 2.0 Page Life Cycle - The lifetime of an ASP.NET page is filled with events. A series of processing steps takes place during this page life cycle. Following tasks are performed:* Initialization* Instantiation of controls* Restoration & Maintainance of State* Running Event Handlers* Rendering of data to the browserThe life cycle may be broken down into Stages and Events. The stages reflect the broad spectrum of tasks performed. The following stages take place1) Page Request - This is the first stage, before the page life cycle starts. Whenever a page is requested, ASP.NET detects whether the page is to be requested, parsed and compiled or whether the page can be cached from the system.2) Start - In this stage, properties such as Request and Response are set. Its also determined at this stage whether the request is a new request or old, and thus it sets the IsPostBack property in the Start stage of the page life cycle.3) Page Initialization - Each control of the page is assigned a unique identification ID. If there are themes, they are applied. Note that during the Page Initialization stage, neither postback data is loaded, nor any viewstate data is retrieved.4) Load - If current request is a postback, then control values are retrieved from their viewstate.5) Validation - The validate method of the validation controls is invoked. This sets the IsValid property of the validation control.6) PostBack Event Handling - Event handlers are invoked, in case the request is a postback.7) Rendering - Viewstate for the page is saved. Then render method for each control is called. A textwriter writes the output of the rendering stage to the output stream of the page's Response property.8) Unload - This is the last stage in the page life cycle stages. It is invoked when the page is completely rendered. Page properties like Respone and Request are unloaded.Note that each stage has its own events within it. These events may be used by developers to handle their code. Listed below are page events that are used more frequently. PreInit - Checks the IsPostBack property. To create or recreate dynamic controls. To set master pages dynamically. Gets and Sets profile propety values.Init - Raised after all controls are initialized, and skin properties are set. InitComplete - This event may be used, when we need to be sure that all initialization tasks are complete.PreLoad - If processing on a control or a page is required before the Load event.Load - invokes the OnLoad event on the page. The same is done for each child control on the page. May set properties of controls, create database connections.Control Events - These are the control specific events, such as button clicks, listbox item selects etc.LoadComplete - To execute tasks that require that the complete page has been loaded.PreRender - Some methods are called before the PreRenderEvent takes place, like EnsureChildControls, data bound controls that have a dataSourceId set also call the DataBind method.Each control of the page has a PreRender event. Developers may use the prerender event to make final changes to the controls before it is rendered to the page.SaveStateComplete - ViewState is saved before this event occurs. However, if any changes to the viewstate of a control is made, then this is the event to be used. It cannot be used to make changes to other properties of a control.Render - This is a stage, not an event. The page object invokes this stage on each control of the page. This actually means that the ASP.NET server control's HTML markup is sent to the browser. Unload - This event occurs for each control. It takes care of cleanup activities like wiping the database connectivities.

Reference :
http://dotnetuncle.com/Aspnet/71_page_life_cycle.aspx

How Garbage Collector will work in .Net and how to use it?

The most and one of the complex things to handle in .net is Garbage Collector(I feel). To find out more on these.........

Some of the best articles i have seen on Garbage Collector and how the GC(Garbage Collector) works in .net.

Very use ful links :
http://www.codeproject.com/KB/dotnet/gcbyleslie.aspx
http://www.csharphelp.com/archives2/archive297.html
http://msdn2.microsoft.com/en-us/library/0xy59wtx.aspx

Here are some tips on the frequently asked questions in Interviews.

A few days back when search for a quick review of topics in .net, i found this link is very useful.
I hope the same will help you for the quick reference.
With topic-wise........

http://dotnetuncle.com/

Here is the full presentation on how to create a webservice

The buzz word around IT these days is Web Services. A web service is not a website that a human reads. It is not anything with which an end user would directly interact. A web service is a standard platform for building interoperable distributed applications. It allows you as a developer, to interact with other information providers without worrying about what they are running either at the backend or even their front-end. Take for example a company stock ticker that you may wish to have, say on your website or intranet. The data could possibly be coming from a major news site like MSN or NASDAQ. The way you would currently achieve this is either by buying access to their database or by ‘scraping’ their home page HTML for the relevant data and converting it into your format. Suppose they go ahead and change their web design, all the scraping code you would have written would be rendered useless. Even if you buy access into their system, they may be running a technology that is incompatible or too hard to work with your own.

Follow up the link for more information.

http://www.codeproject.com/KB/IP/intro2websvc.aspx

UDDI from W3Schools

What is UDDI
UDDI is a platform-independent framework for describing services, discovering businesses, and integrating business services by using the Internet.
UDDI stands for Universal Description, Discovery and Integration
UDDI is a directory for storing information about web services
UDDI is a directory of web service interfaces described by WSDL
UDDI communicates via SOAP
UDDI is built into the Microsoft .NET platform
What is UDDI Based On?
UDDI uses World Wide Web Consortium (W3C) and Internet Engineering Task Force (IETF) Internet standards such as XML, HTTP, and DNS protocols.
UDDI uses WSDL to describe interfaces to web services
Additionally, cross platform programming features are addressed by adopting SOAP, known as XML Protocol messaging specifications found at the W3C Web site.
UDDI Benefits
Any industry or businesses of all sizes can benefit from UDDI
Before UDDI, there was no Internet standard for businesses to reach their customers and partners with information about their products and services. Nor was there a method of how to integrate into each other's systems and processes. Problems the UDDI specification can help to solve:
Making it possible to discover the right business from the millions currently online
Defining how to enable commerce once the preferred business is discovered
Reaching new customers and increasing access to current customers
Expanding offerings and extending market reach
Solving customer-driven need to remove barriers to allow for rapid participation in the global Internet economy
Describing services and business processes programmatically in a single, open, and secure environment
How can UDDI be Used
If the industry published an UDDI standard for flight rate checking and reservation, airlines could register their services into an UDDI directory. Travel agencies could then search the UDDI directory to find the airline's reservation interface. When the interface is found, the travel agency can communicate with the service immediately because it uses a well-defined reservation interface.
Who is Supporting UDDI?
UDDI is a cross-industry effort driven by all major platform and software providers like Dell, Fujitsu, HP, Hitachi, IBM, Intel, Microsoft, Oracle, SAP, and Sun, as well as a large community of marketplace operators, and e-business leaders.
Over 220 companies are members of the UDDI community.

For more info follow up this article.
http://www.w3schools.com/WSDL/wsdl_uddi.asp

Web Services Description Language (WSDL) 1.1

WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate, however, the only bindings described in this document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.
Please follow up this article for more information.

http://www.w3.org/TR/wsdl

Here is the proffessional comparision and difference between C# and VB.Net

Hey,
I have been searching on web for a while on C# and VB.Net language differences.

I found these two articles were really useful.
Please follow up and find yourself in the comparision.

http://www.harding.edu/fmccown/vbnet_csharp_comparison.html
http://www.codeproject.com/KB/dotnet/vbnet_c__difference.aspx

Here are the cool links on our favourite web services.

Hello every one,

Here you can find some cool stuff and some work arounds on web services.
Have fun.

http://quickstart.developerfusion.co.uk/quickstart/webservices/
http://msdn2.microsoft.com/hi-in/webservices/default(en-us).aspx
http://www.15seconds.com/issue/010430.htm

Sending Files in Chunks with MTOM Web Services and .NET 2.0

Send the files what ever you want from your application to any application.

In trying to keep up to speed with .NET 2.0, I decided to do a .NET 2.0 version of my Code Project article DIME Buffered Upload, which uses the DIME standard to transfer binary data over web services. The DIME approach is reasonably efficient, but the code is quite complex and I was keen to explore what .NET 2.0 had to offer. In this article, I use version 3.0 of the WSE (Web Service Enhancements), which is available for .NET 2.0 as an add-in, to provide a simpler and faster method of sending binary data in small chunks over HTTP web services.

The all you need for your questions and problems, here is the one deastination (For developers only..)

Hello Developers around me and also the world,
Please refer the following site for all your coding related queries and problems.

www.codeproject.com

And try to do some postings in , so that people like us will benefit from the knowledge.

Have fun with web services.

Microsoft .NET marketing has created a huge hype about its Web Services. This is the first of two articles on Web Services. Here we will create a .NET Web Service using C#. We will look closely at the Discovery protocol, UDDI, and the future of the Web Services. In the next article, we will concentrate on consuming existing Web Services on multiple platforms (i.e., Web, WAP-enabled mobile phones, and windows applications).

What is a Web Service?
Web Services are a very general model for building applications and can be implemented for any operation system that supports communication over the Internet. Web Services use the best of component-based development and the Web. Component-base object models like Distributed Component Object Model (DCOM), Remote Method Invocation (RMI), and Internet Inter-Orb Protocol (IIOP) have been around for some time. Unfortunately all these models depend on an object-model-specific protocol. Web Services extend these models a bit further to communicate with the Simple Object Access Protocol (SOAP) and Extensible Markup Language (XML) to eradicate the object-model-specific protocol barrier.

Read more here at..

http://www.15seconds.com/issue/010430.htm and one more article at
http://www.15seconds.com/issue/010530.htm

Which is the BEST to Choose from VB.Net and C#.Net

Hi All,
Sorry for not updatting the blog for a few days.
And here is an interesting debate to start:
Which is the best language to choose from VB.Net and C#.Net.

As I have worked on C#.Net over 2+ years, just i started my work on VB.Net.
Anyways it is going smoothly.
But I want to start a debate on this, which is better.
Please write to me at: zulu.damodar@gmail.com
coz i want to share the information with you all.

Features of Visual Studio 2005. oops.. very use ful

Refractoring Making changes to your code like, "pulling a large stretch of inline code into its own method" or "converting a field to be a property." The Refactoring support makes this easy to do The key tenet of Extreme Programming created by Kent Beck is constant Refactoring. Under this programming model, you are developing code rapidly and iteratively, but to keep your code from becoming a jumbled mess, you must constantly Refactor. Refactoring is a C# only feature[enter][/center]
Edit and Continue Visual Basic has always been about Rapid Application Development (RAD). One key feature is the ability to fix runtime errors on the fly. With Visual Basic .NET 1.0 and Visual Basic .NET 1.1, this powerful feature wasn't included. This feature is on-board for Whidbey. If you run into an exception at runtime, you get an exception helper that provides tips for fixing common errors, but more importantly, you can edit the code, select F5, and it continues right where you left off. Edit and Continue is VB .NET only feature
ClickOnce ClickOnce make it easy to install applications and provide ongoing updates (Self-Updating), rather than forcing to distribute new versions of application, can just deploy the portion of the application which has changed. In the .NET Framework 1.0 and 1.1, href-exes were not able to solve many deployment issues. Href-exes are also known as ''no-touch deployment, or zero impact deployment''. Essentially, with versions 1.0/1.1, you can deploy an application to a Web server, allowing users to browse to the URL for the exe, as in: You can run me by clicking this link When the user clicks the link, the application downloads to their Internet files cache and runs. To keep this from being a huge security hole, the application permissions are restricted based on the URL (Intranet applications get different permissions than Internet applications, for example), or other factors. This means that some applications no longer need to be deployed in the traditional sense; no more setup.exe or MSI
href-exes have a number of limitations
The .NET Framework must be pre-installed on the client machine.
There's no good way to bootstrap the .NET Framework down if it's not there.
Most non-trivial applications consist of the main .exe and a number of assembly files. With href-exes, the assembly files are downloaded on demand, which is great for corporate Intranet applications, but there's no way to download the application in one shot so that you know it can be safely used off-line.
Limited support for versioning.
The application doesn't hook into Add/Remove Programs, and the application doesn't install Start menu shortcuts.
ClickOnce deployment differs from href-exes in some significant ways
ClickOnce applications are self-updating.
With href-exes you can only make the application self-updating through the use of custom code or through the use of a component, such as the .NET Application Updater component.
With ClickOnce, updates can also be marked as mandatory or optional.
When applications are installed through ClickOnce, they show up in the start menu and they can be uninstalled through the '''Add/Remove Programs''' feature.
ClickOnce works its magic through two XML manifest files.
The first is an ''application manifest'' and
The second is a ''deployment manifest''.
The application manifest describes the application itself, which includes information about the application assemblies, dependencies, and files that make up the application. The application manifest also states the required permissions, and the location where updates can be downloaded.
The deployment manifest points to the location of the application manifest and files, and instructs the clients on which version of the application they should be running.
SmartTags This provides access to information and common tasks without forcing you to constantly navigate away from your work area [enter][/center]
Code Snippets With code snippets, you can insert generic "template" code that requires only that you fill in the blanks. You can access code snippets by right-clicking in the code editor and navigating in the context menu to Insert Snippets [enter][/center]
Exporting IDE Settings With Whidbey, migrating and persisting IDE settings are a simple process of navigating to Tools Import/Export Settings. [enter][/center]
Line Revision Marks Line Revision marks allow you to see the changes you've made during a coding session. When writing code in the IDE, you'll notice yellow and Lime lines appearing down the left hand side of the code editor window. [enter][/center]To change the color, navigate to '''Tools Options''' in the IDE, and then choose '''Show All Settings'''. After that expand '''Environment''' click on the '''Fonts and Colors'''. Scroll down the '''Display Items'''
'''Track changes before Save''' - yellow
'''Track Changes after Save''' - Lime
Temporary Projects Visual Studio .NET 2002 and Visual Studio .NET 2003 both had a propensity to persist your temporary ideas as permanent projects on your hard disk. This created the ''WindowsApplication1,2,3...n'' problem. Visual Studio .NET supports the idea of temporary projects. if you attempt to close the IDE without saving, it will prompt you to either save or ''discard'' the project
About the author Vidya Vrat Agarwal, a Microsoft .NET Purist, and a MCSD.NET, MCAD.NET, MCSD, MCT. He is also a Life Member of Computer Society of India (CSI). He started working on Microsoft.NET with its beta release. He has been involved in software development, corporate trainings, T3 programs, technical writing and consultation for Microsoft.NET for various corporate clients. Presently he is working with LionBridge Technologies in Mumbai - India, where he works with Microsoft Dept. on Whidbey and Yukon and his business card reads Subject Matter Expert His technical profile holds .NET Framework, VC#, VB.NET, WebServices, Remoting, SQL Server, COM, DCOM, COM+, MTS, MSMQ. Whidbey, Yukon and Longhorn.