Are you by any chance running on a 64 bit platform? The extensions are
currently only available for 32 bit platforms.

No i am using 32 bit....................

Are you running VS on your server or workstation? You need to be able to
reference the object model, which means working on the server or copying the
SharePoint DLLs to your client.

Have a look at this excerpt (written for VS 2008). Article is at
www.sharepointblogs.com/.../sharepoint-2007-w
orkflow-with-visual-studio-2008.aspx

If you're on a MOSS2007 server then simply create a new Sequential Workflow
project. If not you'll need to grab the sharepoint  DLLs from the server, the
easiest way of doing this is to take microsoft.sharepoint.* and
microsoft.office * from the servers C:\Program Files\Common Files\microsoft
shared\Web Server Extensions\12\ISAPI directory and create and copy to the
same path on your development machine. You will now have all the references
you need to create a workflow project, go ahead and simply create a new
Sequential Workflow project.

I've never tried this, but it may work.

Here's a tutorial on the whole process of creating workflows  in VS2005,
which may have some other ideas.

Developing SharePoint Workflows Using VS 2005

msevents.microsoft.com/.../...astEventDetails.aspx
ntID=1032301596&CountryCode=US

I am running VS 2005 on my local machine, so are you saying i have to
have vs on the same machine as sharepoint?

No, but you have to have a copy of the SharePoint DLL's on the local machine to
write code against. You'll be able to write and compile workflows, but you
won't be able to debug or test them on your local machine.

Ø I am running VS 2005 on my local machine, so are you saying i have to

Ø have vs on the same machine as sharepoint?

Yes, or copy the DLLs to your workstation (read the entire post!), which
will probably present other problems during compilation/ deployment.
Virtually every article that I have read on sharepoint  development
recommends the server option, unless you are developing a client application
that uses Web Services rather than the Object Model.

For what it's worth, I have developed (web parts, not workflows) using the
local DLL approach; it was about a year ago, but I don't remember any
particularly troublesome issues as a result of that method.

you have to deploy them to the server to test/debug
them, which can get irritating after several iterations … especially if you
code like I do.

When you are saying copy the sharepoint  DLLs to your client. Where
would I find those and where would I copy them to the client. It
seems more that i look into sharepoint that cutomization is very
hard. And you should do all development on the sharepoint box, i.e.
infopath, designer.

I have a virtual pc that has all the applications on it, to include
infopath, designer, vs, sharepoint. So when i go to the C:\Program
Files\Common Files\microsoft shared\Web Server Extensions\12\ISAPI
folder the dll are there. I still get the error The project type is
not supported by this installation.

If you are running visual  studio in a VPC that also contains SharePoint then you
shouldn't be getting that error unless you installed the wrong version of the
extensions. There are extensions for SharePoint 2003 that won't work on 2007
and there are also extensions for SharePoint that are specific to Visual Studio
2005 and Visual studio  2007. What version of SharePoint are you running, what
VS, and what version of the extensions did you download and install?

I finally got it:

Visual Studio 2005 Extensions for Windows Workflow Foundation (EN).exe

- You would think that all the extensions you need would come bundle
with Visual Studio 2005.

- Ok now where do I go :), Are there any good webcast that show how
to build a task review workflow, or maybe a simple review workflow so
I can get an idea how to build workflows  is VS 2005