Hi David,
If it worked, would it give me error information as to where the XML was
failing?
Best wishes.
Tim Burgess
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On
Behalf Of reynoldsdavid46@xxxxxxxxx
Sent: 19 April 2022 14:32
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: Buying Visual Studio Professional
Hi Tim,
Rather than go to that expense, have you tried opening the XML file in a
browser. This worked for me back in the day, but you may need a CSD file to
make that happen successfully.
Best,
David.
From: program-l-bounce@xxxxxxxxxxxxx <mailto:program-l-bounce@xxxxxxxxxxxxx>
<program-l-bounce@xxxxxxxxxxxxx <mailto:program-l-bounce@xxxxxxxxxxxxx> > On
Behalf Of Tim Burgess
Sent: 19 April 2022 09:49
To: Program-L <program-l@xxxxxxxxxxxxx <mailto:program-l@xxxxxxxxxxxxx> >
Subject: [program-l] Buying Visual Studio Professional
Hi,
Ive been successfully using VS2019 Community Edition for a while, as Im
well under the $1,000,000 revenue threshold (who isnt?:). However, Ive
just read that one of the few differences between Community and Pro is the
ability to use XML debugging and I find myself needing to figure out whats
wrong with a very small XML file in order to try and save a project for a
client.
Google throws up a bunch of companies who will sell me a VS2019 or VS2022
product key for a few tens of GBP, but are these legitimate? I last
purchased a CD-based Pro version for VS2008 and it was about £400, so Im
suspicious and want to make sure that Im operating legitimately. Similarly,
I dont really want to drop a few hundred quid for a couple of hours
debugging unless I really have to.
Any advice, please?
Best wishes.
Tim Burgess
Raised Bar
tim@xxxxxxxxxxxxx <mailto:tim@xxxxxxxxxxxxx>
+44 (0)7989 486976
