Custom NEW User Setup

ASP.NET 2.0 introduces a Web Part control that is designed to deal with the serialization, storage, and retrieval of customization and personalization data behind the scenes. In this article, the authors explain how you can put the WebPart control to work in your ASP.NET 2.0 applications.

Ted Pattison and Fritz Onion

MSDN Magazine September 2005

Database setup can be a tough and time-consuming process and sometimes fall victim to human error. Microsoft Installer or InstallShield can help, as can your own custom installer. In this article, the author tackles one approach to writing database installers and demonstrates the process with a working code sample.

Alek Davis

MSDN Magazine September 2004

There are plenty of options out there for managing user preferences including custom configuration files, the Windows registry, and the isolated storage. But each option has its pros and cons -- and a bad choice can make life difficult. In this article, the author evaluates various options and identifies the characteristics of a good preferences API. Based on those characteristics, he introduces an API that is specifically designed for preferences management, one that offers the best of all the options.

Ray Djajadinata

MSDN Magazine July 2004

Office InfoPath 2003 is a new Microsoft Office product that lets you design your own data collection forms that, when submitted, turn the user-entered data into XML for any XML-supporting process to use. With an InfoPath solution in place, you can convert all those commonly used paper forms into Microsoft Office-based forms and end the cycle of handwriting and reentering data into your systems. Today organizations are beginning to realize the value of the mountains of data they collect every day, how hard it is to access it, and are striving to mine it effectively. InfoPath will aid in the design of effective data collection systems. Here the author shows you how to get started.

Aaron Skonnard

MSDN Magazine September 2003

We recently migrated our document management system to SharePoint (WSS 3.0) and I adapted my VB6 client application to search for and retrieve a list of documents from this new SharePoint library using the Lists web service. Although the total number of documents in this library is 90,000 at one site and over 145,000 at another, my VB6 application never retrieves more than 600-700 documents at a time. From reading white papers such as "Working with Large Lists in Office SharePoint Server 2007" (http://go.microsoft.com/fwlink/?LinkId=95450&clcid=0x409), it appears that if my custom user interface limits the number of items returned in a search of these large lists, that it may not be necessary to put these documents into folders. However, our current scanning software, KnowledgeLake Capture, by default places newly scanned documents into folders based on the year, month, day and hour, which means that these documents are placed in nested folders 4 levels deep.

There are also some 20 metadata fields on these document libraries that allow us to filter these document libraries so that search results will in most cases be limited to a few hundred items.

We acquired new servers (Windows Server 2008 with SQL Server 2008) to host our SharePoint libraries and we are running WSS 3.0 S

Hi ,

I have created a custom user property,and created metadata property and added mapping to it, still i m not able to Search in People,Please advise

Hi,

I have been struggling for a couple of days, trying to set up a decent
structure for an Infopath project using a custom workflow using Visual Studio 2008.

I had a solution with two projects:

1) Sharepoint 2007 Workflow

2) Infopath 2007 form w/code-behind.

I included the xsn, in the VS solution, but after a day or two,
something went wrong, and I lost some work. I still do not know what
happened, but I could not get my changes to persist afterthat  Doing research I have read that this
stucture, using Infopath xsn, within VS does not work correctly with Source
Control. I am using VSS.

So I since made a change to the set-up so that the .xsn (form template) is separate from
Visual Studio. However, I need to leave the code-behind in VS, since I need to debug
it.

This is my latest problem. I have been unable to attach to the correct
process, as VS generates cachse files, and who knows what else.

My question is simple. What is the supported method for debugging InfoPath
code/behind, which uses a Sharepiont Workflow?

I just also want to say that one should not have
to spend a few days just trying to setup a working development environment.

This should be trouble-free, but it is far from being so. I