Nik Ivancic

Please consider this as a plea for help - not a complaint

I just downloaded and installed the newly released .NET 3.0 RC (Release Candidate) as well as the Update for Windows Communication Foundation (KB912817) which has likely nothing to do with WWF, so I am mentioning it here for the completeness sake. In addition, I installed the Visual Studio Extensions for Windows Workflow Foundation RC4, after the RC5 failed to install. Finally, I installed the Hands On Labs from

http://wf.netfx3.com/files/folders/documentation/entry4919.aspx

Then, I tried to re-create the Lab1 and found that everything behaves as it should, I was able to compile the application with no errors. However, setting the break point does not cause the application to stop in the debugger - even if the break point is visible on the Workflow1.xoml (graphically) and the Workflow1.xoml.cs.

I also observed that setting the break-point in the "designer" does not cause the break point being set in the C# code view - nor vice versa. So, I set it on both views, but the application still runs as if there is no breakpoint set.

And yes, I used the "start debugging" green triangle to start the workflow's execution.

Some previous releases of the WWF required the installation of the WWF "SDK", which I did not find for the .NET 3.0 RC so, I did not install any (i.e. I thought that Visual Studio Extensions have all I need to run the labs)

What's going on

Thanks for your help




Re: Windows Workflow Foundation Consistent set of components

Serge Luca

Hi Nik,

-you don't have to install the WF SDK to build your WF app; you only need the .Net 3.0 RC framework (-> dll will be installed in the Gac and in C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\) and if you want to manage it(design, build, compile, debug) from VStudio you need the VS Extension for WF (here RC5).

If you want additional tools, doc, samples etc, then you have to install the SDK...

In your case, try to reinstall the extensions (did you remove the previous build ->use the uninstall tool )

Here is what I did (I come from WF RC4) (The sequence is probably important).

1°„. Read the Net framework 3 RC1 infos:
http://msdn.microsoft.com/windowsvista/support/relnotes/netfxRc1/default.aspx

2°„Uninstall the previous builds

.Net framework 3 uninstall Tool:
http://www.microsoft.com/downloads/thankyou.aspx familyId=AAE7FC63-D405-4E13-909F-E85AA9E66146&displayLang=en&oRef=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdetails.aspx%3fFamilyId%3d19E21845-F5E3-4387-95FF-66788825C1AF%26displaylang%3den

3°„Install .Net framework 3 RC1
http://www.microsoft.com/downloads/details.aspx FamilyId=19E21845-F5E3-4387-95FF-66788825C1AF&displaylang=en


4°„.Install Net 3 RC1 sdk
http://www.microsoft.com/downloads/thankyou.aspx familyId=117ECFD3-98AD-4D67-87D2-E95A8407FA86&displayLang=en&oRef=http%3a%2f%2fwww.microsoft.com%2fdownloads%2fdetails.aspx%3fFamilyId%3d19E21845-F5E3-4387-95FF-66788825C1AF%26displaylang%3den

5°„Install Vs2005 extensions for WF RC5
http://www.microsoft.com/downloads/details.aspx FamilyID=e8232f93-48f0-4e74-b09d-b51f1d4231a4&DisplayLang=en

Hope this helps

Serge






Re: Windows Workflow Foundation Consistent set of components

Nik Ivancic

Hi, Serge

Thanks for such nice collection of advices. I decided to go ahead and follow them literally, including the removal of the .NET 3.0 RC1, which installed without a problem two days ago. So, using the uninstall tool, mentioned in item 2. I got the prompt to do something with SQL Server 2005 configuration files, offer which I rejected as it stated that SQL Server 2005 would stop working if I accept it. This, by the way happened before I installed the .NE 3.0 RC1 (I used the same .NET 3 uninstall tool then as well).

I am not sure whether this caused my original problems (not being able to install the VS 2005 Extension rc5, and breakpoints in workflows not working), but I will continue execetuing your "recipe", and will report back what happened.

Thanks again






Re: Windows Workflow Foundation Consistent set of components

Nik Ivancic

Current summary

I uninstalled everything from the .NET 3.0 rc1, Windows SDK, Visual Studio Extensions RC4 set of components.

Installed the .NET 3.0 RC1 again

Install of the Visual Studion Extensions RC5 failed the same way the installation of the SDK failed for me yesterday (some file was found missing). So, it seems that the Visual Studio 2005 Extensions for WWF is similar or identical in contents to the SDK. I reported this problem to the Microsoft's support group and at the moment, I cannot do anything except to wait.

Any advice would be much appreciated.






Re: Windows Workflow Foundation Consistent set of components

Serge Luca

I find very strange that both installations failed; what was the error message which files were missing

Serge






Re: Windows Workflow Foundation Consistent set of components

Nik Ivancic

No easy way to find out - I looked at the log of the installation which failed, without much success. If you would be kind enough to have a peek, I can send it to your email address.

Regards






Re: Windows Workflow Foundation Consistent set of components

Nik Ivancic

Just realized that I did not report all details of my problem: I used the Microsoft's prerelease WinFX runtime uninstall tool to remove all eventual leftovers from previous beta versions of vista. This tool eventually prompted me to allow the removal of Microsoft SQL Server Setup Support files (why ), with the warning that if I proceed with this, the SQL 2005 Integrations Services, SQL Server itself and SQL Server 2005 tools will be "broken".

Thi seems like to steep price to pay, so I did not allow this step. This may be the reason for my problems and I would appreciate if someone can advise me here.






Re: Windows Workflow Foundation Consistent set of components

Tom Lake - MSFT

Were you able to resolve your installation problem Have you tried installing the release build Links to install location can be found here. Back to your original problem, not breaking on an activity in the workflow when debugging. If you have a break point in the code beside do it break on that If so, you probably don't have a Workflow project as the startup project. Right click on the workflow project and choose Set as StartUp Project. If it is a dll project right click on the project and choose Properties. On the Debugger tab under Start Action select Start external program and point to the exe created by the original startup project.