Agility pack step 1

Topics: User Forum
Jul 11, 2007 at 9:25 AM
Hi,

I'm using visual studio 2005 and have what is likey to be considered a stupid question.

I've downloaded the agility pack. When I open the solution file I get an error saying

>>" The source control provider associated with this solution could not be found. The projects will be treated as not under source control. Do you want to permanently remove the source control bindings from the projects?" <<

Then if I try to run any of the files(samples) in visual studio I get this error

>>"A project with an output type of class library cannot be started directly. In order to debug this project, add an executable project to this solution which references the library project. set the executablle project as the startup project"<<

I'm guessing theres more to get the samples running than just opening the files? From what I can see theres no information on how to set up in the documentation.

Im new to visual studio and am having trouble finding out how to resolve the error messages above.

Please help if you can,

thanks,
dub
Jul 13, 2007 at 1:18 PM
dubeat:
The two errors you're seeing are unrelated - but the important one (ie the one that's stopping you run any of the samples) is the second - less an error and more a badly written info message: you need to set a sample project as your start up project (otherwise VS will try and build and run a dll - hence the class library cannot be started directly error ) - right click the sample you want to run, and in the context menu that appears, click on 'Set as Startup Project'. Then when you F5 (build n run) the project you set as the start up will launch. If you want to use the HtmlAgilityPack functionality in another project - then build the project HtmlAgilityPack under release mode. This will create a dll you can reference in new projects - youll need to add a reference to the newly built dll and add a 'using HtmlAgilityPack;' line to your using references. Hope this vaguely helps.
Feb 8, 2008 at 2:29 PM
This issue is caused by source control bindings embedded within the project's source files. You can safely ignore this message. Once you do that, you will be prompted (in Visual Studio 2005 anyway) to permanently remove these bindings. Answering yes removes the bingins and ensures that you dont see the message again.


Here is a nice post on different options for handling this issue: http://blogs.msdn.com/korbyp/archive/2003/12/17/44209.aspx