Workflow Extensions RC5 not working?
-
Tuesday, September 12, 2006 6:12 PM
I have installed RC1 of the .NET 3.0 framework ok on my Windows XP x64 workstation, but the Workflow Extensions RC5 for Visual Studio 2005 don't seem to work.
They install the SDK but no Workflow options appear in VS2005
The previous CTP (July) worked ok?
All Replies
-
Tuesday, September 12, 2006 10:40 PMModeratorCan you share the install locations of your current configuration?
-
Wednesday, September 13, 2006 5:38 AM
SDK (from extensions install) seems to be installed in C:\Program Files\Microsoft SDKs\Windows\v6.0
Framework RC1 installed in C:\WINDOWS\Microsoft.NET\Framework\v3.0 and also C:\WINDOWS\Microsoft.NET\Framework64\v3.0
-
Wednesday, September 13, 2006 5:45 AM
Howard, there are two neccesary installs to develop workflows (the runtime and the extensions for Visual Studio). Everything else is optional (SDK, Orcas tools, etc).
See Paul's post here. It sounds like you installed the SDK and the runtime, you'll need to install the extensions as well.
Let me know if that doesn't work.
-
Wednesday, September 13, 2006 7:16 AM
Doh! If I had looked at the start menu items I would have noticed I needed to manually register the SDK with VS2005.
I was used to the previous extensions self-installing.
thanks for the help
-
Wednesday, September 27, 2006 1:55 AMHow do I "manual" register the SDK with VS2005? I run the "Register Windows SDK Directories with Visual Studio 2005" and any thing happen.
how can I install the Visual Studio Extentions? When I run "Visual Studio 2005 Extensions for Windows Workflow Foundation RC5(EN).exe" I always get the modify screen from SDK. If I install from the begin, installs the SDK.
how can I install the Visual Studio Extentions?
tkx in advance
Paulo Aboim Pinto -
Wednesday, September 27, 2006 12:56 PM
Hi there,
I have recently failed into the same issue.
So after I have installed the SDK, I went to <windows folder>\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation\ and started the WF_3.0_x86.msi and it added the Extenstions to Visual Studio.
Hope this helps!
-
Sunday, October 01, 2006 3:04 PMHello
I've done what you suggest and I have the same efect. There is no VS Extentions installed.
Any one can help me?
tkx in advance
Paulo Aboim Pinto -
Tuesday, October 03, 2006 6:05 AM
Hi, there,
I had the exact the same problem when I saved the rc5 msi locally and then installed it. I managed to bypass this problem by clicking the Run button directly on the File Download Dialog. Try it, it might help.
Richard
-
Wednesday, October 04, 2006 12:46 AMtanks ... finally works.
Can anyone explain this?
Paulo Aboim Pinto
Odivelas - Portugal -
Friday, October 06, 2006 5:48 PM
I cannot install the extensions for visual studio.
I have installed everything, including wpf, and wcf but I cannot get the wf project available in visual studio!!!
I read the previous posts but I didn't solve the problem.
Any help??
-
Friday, October 06, 2006 8:10 PM
If you run the MSI for the WF extensions from the same directory where you have a setup.exe file (like the Windows SDK installer) then when the WF extensions are extracted, the wrong setup file gets run. When you run the installer, you should not get the SDK install dialogs, but a unique WF extensions dialog.
Simply rename the Windows SDK installer to something else and you should be good to go.
Matt
-
Saturday, October 07, 2006 2:22 PM
Thanks a lot!!
A folk told me about this strange behavior yesterday when I was about to reinstall the whole sdk, framework, and extensions again!
Renaming the sdk solved the problem.
Bye
-
Sunday, October 15, 2006 10:17 AMI had all the installation files on my desktop. And i got the same behaviour...Then i moved the Visual Studio 2005 Extensions for Windows Workflow Foundation RC5(EN).exe to a different folder (%my documents%) and i suddenly got to see the right installer ;))Thanks.
-
Tuesday, October 17, 2006 8:32 PM
I had a similar problem. Running the RC5 .exe launched the Live Meeting Installer(?). No clue why? So, I extracted the contents of the .exe into a directory and run the extracted setup.exe from there and everything worked ok.
Later

