XSharp Bandol Beta 9 "Winter has come"

I after I installed Bandol Beta 9, all my projects appear as "unavailable". After re-installing beta 8, I re-opened the same solution, I can see all the projects again.

Boonnam,

[quote name="Boonnam S"]I after I installed Bandol Beta 9, all my projects appear as "unavailable". After re-installing beta 8, I re-opened the same solution, I can see all the projects again.[/quote]
What exactly do you mean with 'unavailable' , 'unloaded' (in which case you can right click and load the project) or was the project system not there and were you not able to reload the project ?
And which version of VS are you using (full version number please)?

Robert

Unfortunately I cannot attach a file to this thread to show you. But it look something like this:
QL32 (unavailable)

After I attempt to reload the project, I get an error:
Access to the path

'C:\TFSCloud\Development\QLA6_V1.0Migration\QLAdmin-MSDev\QL32\QL32.xsproj.backup' is denied.

Then I can see "QL32 (load failed)".

It still work if I re-install beta 8.

I forgot to mention that XSharp extension is enabled.

[quote name="Boonnam S"]Unfortunately I cannot attach a file to this thread to show you. But it look something like this:
QL32 (unavailable)

After I attempt to reload the project, I get an error:
Access to the path

'C:\TFSCloud\Development\QLA6_V1.0Migration\QLAdmin-MSDev\QL32\QL32.xsproj.backup' is denied.

Then I can see "QL32 (load failed)".

It still work if I re-install beta 8.

I forgot to mention that XSharp extension is enabled.[/quote]
Boonnam,

If you want to attach images you should use the forum for messages. There you have the ability to do that.
Comments are usually used for short comments that do not need images.

But I think I know what the problem is: is it possible that there is a readonly version of the .backup file in the folder. Could you rename that or delete the backup and try again?

I know that the project system tries to update the xsproj file (we made the "include path" and "nostandarddefs" configuration independent. During that process it copies the current xsproj file to the backup. Maybe an exception occurs if the backup already exists and is readonly.

Robertt

I deleted all ".backup" files. Still have same issue.
I made all ".backup" files write-able. Same issue.
I deleted all the folders, and re-load from the TFS. Same issue.

Also, one other developer who also installed beta 9 have same issue.

Boonnam,

Which version of VS ?
And you say that one other has the same problem. Are there others that can work with beta 9 without problems?
If so, can you compare the versions of VS and other extensions ?

Robert

We both are using VS 2017 (professional). My version is version 15.9.4. I see that I have updates available for VS. Currently only two developers (me included) have tried using beta 9.

[quote name="Boonnam"]We both are using VS 2017 (professional). My version is version 15.9.4. I see that I have updates available for VS. Currently only two developers (me included) have tried using beta 9.[/quote]
Boonnam,
Please try this:
- before opening the solution make sure that all the xsproj files are read/write: there is a scenario when the project system makes backup files of your project twice. When the original xsproj is readonly then the first backup will also be readonly and therefore the second backup could fail.
If that does not work then please mail me the sln and xsproj files. No need to send the prg files.
Robert

It works! Thank you very much!

Boonnam,

[quote name="Boonnam"]It works! Thank you very much![/quote]

So what did you do? I would like to learn how we can improve this and prevent this from happening again in the future.

Robert