Hello Marenela
I had too many solutions in my download code ThePhileVB .sln and ThePhile.sln , hence 113 default errors.
I questioned it at first but as I am far from experienced I accepted the code as it stood. I made so many attempts to create the same file structure I was extremely discouraged and frustrated. I achieved it in the end but as you might imagine it caused more problems.
After reading a message from Eric
I deleted ThePhile.sln in the download but I was very wary in case it caused extra problems. But it was ok.
I have since come to realise that my download code was wrong so I started my project yet again from scratch. I now have a distrust in the download code.
For example I found the Navigator.
vb file located in Controls\Server has a problem.
Originally:
With xslt
.Load(Context.Server.MapPath(myTransformFilePath))
.Transform(xDoc, Nothing, writer)
It should read
With xslt
.Load(Context.Server.MapPath(myTransformFilePath))
.Transform(xDoc, Nothing, writer, nothing)
Instead of expecting the reader to waste valuable time scouring Forums and reading and re- reading that lengthy Wrox Website Programming Book Notes document, it would be far easier for the author to amend the downloaded code as and when an anomalies are brought to attention (that seems the logical thing to do). I am sure they would gain a lot more respect and loyalty for the books. Instead they choose to issue a variety of amendments, in document format.
I am sure most people would prefer and appreciate updated code, rather than struggle to create a project with incorrect syntax and coding, when they could utilise precious hours furthering the application.
Lynn