Sunday, June 24, 2012 1:18 AM
A quick search of the forum does not seem to find this error message already being discussed.
I am not sure if it is a known issue, but just in case...
In Windows 8 RP with Visual Studio 2012 RC installed
I have Blend pinned to my task bar.
The items in the recent list displayed by right clicking on the Blend task bar icon do not seem to launch correctly and result in the following error message:
"The item you selected is unavailable. It might have been moved, renamed, or removed. Do you want to remove it from the list?"
I have tried the "Yes" option to remove it, which cleared it from the list. I then have navigated back to the solution folder and Opened it with Blend which adds it back to the list. But If I close the solution and then try to use the Recent item from the Right Click approach I once again get the same error.
Blend does not seem to be handle launching recent solutions from the task bar icon correctly.
The same solutions seem to launch fine when I attempt to launch them in a similar manner with Visual Studio (which I also have pinned to the task bar).
I also notice that the icons for the recent items list for blend all seem to use the simple blank page with a folder top right corner icon.
Sunday, June 24, 2012 4:33 PM
Thanks for the feedback. I m unable to repro this on our internal bits. Is your Visual Studio installed in the default location (%ProgramFiles%/ ...) ?.
- Edited by Harikrishna MenonMicrosoft Employee Sunday, June 24, 2012 4:38 PM
Sunday, June 24, 2012 5:55 PM
Yes my VS is installed to that default location.
However, my solutions are not. I prefer to put all of my code in a particular directory of my own C:\Data\Code\... instead of saving to the default user documents folder.
Perhaps that is related?
Sunday, June 24, 2012 9:43 PMTried that too. It looks to be fixed in the latest bits .I will follow up with the right people on our team to make sure that we take a look at this scenario once again. Thanks for reporting this issue :).
Tuesday, August 21, 2012 2:08 AM
The RTM version of Blend for VS does indeed seem to fix this issue.