Home Dashboard Directory Help
Search

Server Explorer Missing by Jungleboy6


Status: 

Closed
 as External Help for as External


0
0
Sign in
to vote
Type: Bug
ID: 335494
Opened: 3/28/2008 7:14:19 AM
Access Restriction: Public
Primary Feedback Item: 337334
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

I have been using VS2008 for a while now...using Server Explorer panel.....and one day I was going to create a DB project and relized it was not there anymore....I have tried to devnet /restoresetttings and still nothing......nothing happens when i click on VIEW > SERVER EXPLORER....same with TOOLS > CONNECT TO DATABASE & TOOLS > CONNECT TO SERVER......I am running out of options here.
Details
Sign in to post a comment.
Posted by SkyTan on 3/24/2010 at 3:30 AM
i also facing the same problem and i already follow the step which delete the DefaultView.SEView but the problem is still unsolve...my server explore still missing (nothing come out when i click View > Server Explore

i am using visual studio 2008 and windows 7

can u help me?

thank
Posted by Microsoft on 4/28/2008 at 8:24 AM
Dear Customer,

Given that I have not heard from you for a week. I will treat the issue as same in (http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=337334).

Thanks!

John Chen (VS BizApps)
Posted by Microsoft on 4/21/2008 at 1:22 PM
Dear Customer,

See also (http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=337334).

Please check to see you have the same issue.
Thanks!

John Chen (VS BizApp)
Posted by Microsoft on 4/18/2008 at 11:12 AM
Dear Customer,

I am the dev investigating this issue now.
I would suggest you to try this out:

Locate the DefaultView.SEView file under his AppData directory and delete it. If this file got corrupted it would cause SE to fail to open.

The file path is hidden, an full path example is like this:
c:\Users\yourusername\AppData\Roaming\Microsoft\VisualStudio\9.0\ServerExplorer

John Chen (VS BizApp Team)
Posted by Microsoft on 3/30/2008 at 11:33 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Sign in to post a workaround.