Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Studio
  4. Top 10 VS.NET IDE annoyances

Top 10 VS.NET IDE annoyances

Scheduled Pinned Locked Moved Visual Studio
visual-studiohelpcsharphtmlcom
4 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    Steven Campbell
    wrote on last edited by
    #1

    Posted partly for fun, partly in case anyone has workarounds... 1) No confirmation when dragging and dropping project items - I like to drag the scrollbar on the project list, but sometimes I grab a file or folder instead. By the time I realise it, I have dragged something to somewhere and am not quite sure what. 2) Lack of tab group management - when working with web projects, the open windows quickly become unmanageable 3) Bookmarks only affect current files - there is a way around this I think, but it is still annoying default behavior. 4) No reverse F12 - the F12 key jumps to a definition, but there is no inverse key combination to go back to where you came from. 5) Wacky HTML Editor - various problems and annoyances, such as poor support for DIV tags, wierd swapping out of some HTML entity codes, etc. 6) No auto-reference fix - when I add references to COM objects, and I recompile my COM dlls, the references break and I have to manually delete and re-add them 7) Solution file locations - When adding multiple projects, the behavior is such that it wants to store the solution file with the first project. From a Source Code control point of view this is annoying, and can cause some funky SourceSafe project trees - it would be better if the solution defaulted to a parent directory. 8) Inability to view codebehind SCC history - you cannot get the history of a codebehind file, unless you show all project files and go directly to the .cs/vb file 9) Crappy XML editor - by which I mean the "data" editor, the "code" editor is fine. 10) Help/Check for Updates fails the first time I click it. The second time gives a different message, but I supect it does nothing really. (I think the reason MS has not yet released any updates for VS.NET is because they are too embarassed that the "Check for Updates" does not work).

    V M B 3 Replies Last reply
    0
    • S Steven Campbell

      Posted partly for fun, partly in case anyone has workarounds... 1) No confirmation when dragging and dropping project items - I like to drag the scrollbar on the project list, but sometimes I grab a file or folder instead. By the time I realise it, I have dragged something to somewhere and am not quite sure what. 2) Lack of tab group management - when working with web projects, the open windows quickly become unmanageable 3) Bookmarks only affect current files - there is a way around this I think, but it is still annoying default behavior. 4) No reverse F12 - the F12 key jumps to a definition, but there is no inverse key combination to go back to where you came from. 5) Wacky HTML Editor - various problems and annoyances, such as poor support for DIV tags, wierd swapping out of some HTML entity codes, etc. 6) No auto-reference fix - when I add references to COM objects, and I recompile my COM dlls, the references break and I have to manually delete and re-add them 7) Solution file locations - When adding multiple projects, the behavior is such that it wants to store the solution file with the first project. From a Source Code control point of view this is annoying, and can cause some funky SourceSafe project trees - it would be better if the solution defaulted to a parent directory. 8) Inability to view codebehind SCC history - you cannot get the history of a codebehind file, unless you show all project files and go directly to the .cs/vb file 9) Crappy XML editor - by which I mean the "data" editor, the "code" editor is fine. 10) Help/Check for Updates fails the first time I click it. The second time gives a different message, but I supect it does nothing really. (I think the reason MS has not yet released any updates for VS.NET is because they are too embarassed that the "Check for Updates" does not work).

      V Offline
      V Offline
      vladfein
      wrote on last edited by
      #2

      For 2) (open documents management) try FeinWindows from FeinSoftware ----------------------------- Get trial copy of comment generating tool CommentMakerPro, std::string and std::string containers viewer FeinEvaluatorPro and windows manager for Microsoft Visual Studio .NET FeinWindows at www.FeinSoftware.com

      1 Reply Last reply
      0
      • S Steven Campbell

        Posted partly for fun, partly in case anyone has workarounds... 1) No confirmation when dragging and dropping project items - I like to drag the scrollbar on the project list, but sometimes I grab a file or folder instead. By the time I realise it, I have dragged something to somewhere and am not quite sure what. 2) Lack of tab group management - when working with web projects, the open windows quickly become unmanageable 3) Bookmarks only affect current files - there is a way around this I think, but it is still annoying default behavior. 4) No reverse F12 - the F12 key jumps to a definition, but there is no inverse key combination to go back to where you came from. 5) Wacky HTML Editor - various problems and annoyances, such as poor support for DIV tags, wierd swapping out of some HTML entity codes, etc. 6) No auto-reference fix - when I add references to COM objects, and I recompile my COM dlls, the references break and I have to manually delete and re-add them 7) Solution file locations - When adding multiple projects, the behavior is such that it wants to store the solution file with the first project. From a Source Code control point of view this is annoying, and can cause some funky SourceSafe project trees - it would be better if the solution defaulted to a parent directory. 8) Inability to view codebehind SCC history - you cannot get the history of a codebehind file, unless you show all project files and go directly to the .cs/vb file 9) Crappy XML editor - by which I mean the "data" editor, the "code" editor is fine. 10) Help/Check for Updates fails the first time I click it. The second time gives a different message, but I supect it does nothing really. (I think the reason MS has not yet released any updates for VS.NET is because they are too embarassed that the "Check for Updates" does not work).

        M Offline
        M Offline
        Michael Dunn
        wrote on last edited by
        #3

        The reverse of F12 is Ctrl+Num Pad * (at least in VC 6) --Mike-- Personal stuff:: Ericahist | Homepage Shareware stuff:: 1ClickPicGrabber | RightClick-Encrypt CP stuff:: CP SearchBar v2.0.2 | C++ Forum FAQ ----

        1 Reply Last reply
        0
        • S Steven Campbell

          Posted partly for fun, partly in case anyone has workarounds... 1) No confirmation when dragging and dropping project items - I like to drag the scrollbar on the project list, but sometimes I grab a file or folder instead. By the time I realise it, I have dragged something to somewhere and am not quite sure what. 2) Lack of tab group management - when working with web projects, the open windows quickly become unmanageable 3) Bookmarks only affect current files - there is a way around this I think, but it is still annoying default behavior. 4) No reverse F12 - the F12 key jumps to a definition, but there is no inverse key combination to go back to where you came from. 5) Wacky HTML Editor - various problems and annoyances, such as poor support for DIV tags, wierd swapping out of some HTML entity codes, etc. 6) No auto-reference fix - when I add references to COM objects, and I recompile my COM dlls, the references break and I have to manually delete and re-add them 7) Solution file locations - When adding multiple projects, the behavior is such that it wants to store the solution file with the first project. From a Source Code control point of view this is annoying, and can cause some funky SourceSafe project trees - it would be better if the solution defaulted to a parent directory. 8) Inability to view codebehind SCC history - you cannot get the history of a codebehind file, unless you show all project files and go directly to the .cs/vb file 9) Crappy XML editor - by which I mean the "data" editor, the "code" editor is fine. 10) Help/Check for Updates fails the first time I click it. The second time gives a different message, but I supect it does nothing really. (I think the reason MS has not yet released any updates for VS.NET is because they are too embarassed that the "Check for Updates" does not work).

          B Offline
          B Offline
          bneacetp
          wrote on last edited by
          #4

          Here's one to add to the list: In Visual C++ .NET, when adding a new class, the implementation file includes the its header file with ".\header.h" instead of "Header.h". For me, this can be a pain. :~ Happy Programming and God Bless! "Your coding practices might be buggy, but your code is always right." Internet::WWW::CodeProject::bneacetp

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups