locked
IDE in Design view RRS feed

  • Pergunta

  • i have just installed vs2005 and have a problem with the design view of the IDE.  i cant place a button or txtbox or the like on the design view and see it.

    the code is there but it is invisible in design view. ive tried resetting all settings but with no look.

    is there a way to turn on the feature that allows for the display of buttons etc in design view.

     

    thanks

    jimkn

    sábado, 25 de novembro de 2006 18:07

Respostas

  • its no bug. Something is wrong somewhere. I can do it fine without any problems.

    go to tools > import and export settings > Reset IDE Settings

    close and restart VS.NET and open the project/create a new project. What happens now? Does it allow you to drag items to the designer layout?

     

    segunda-feira, 27 de novembro de 2006 00:13

Todas as Respostas

  • it shouldnt do this and even resetting the IDE as you stated didnt work which is a bit of a shock. Is this on a new project or from a converted project?
    domingo, 26 de novembro de 2006 03:39
  • hi, i have just deleted everything and installed vs2005 again and still get this problem.

    if i click new website, choose ASP.NET website and visual c#

    select design view

    i can't drag an object from the tool box. i get a circle with a line when i try

    if i double click it will show in the code but not in design view.

    please can you help. have messed with the settings previously or is it a bug

    thanks

    jim

    domingo, 26 de novembro de 2006 23:38
  • its no bug. Something is wrong somewhere. I can do it fine without any problems.

    go to tools > import and export settings > Reset IDE Settings

    close and restart VS.NET and open the project/create a new project. What happens now? Does it allow you to drag items to the designer layout?

     

    segunda-feira, 27 de novembro de 2006 00:13
  • Hi,

     

    Can you help me please for the same problem ?

    i have a Visual Basic Compiler error when i create a winforms project, here's a small dump extract :

     

    AppName: devenv.exe      AppVer: 8.0.50727.762     AppStamp:45716759
      ModName: msvb7.dll      ModVer: 8.0.50727.762      ModStamp:45716a50
      fDebug: 0       Offset: 000088f2

     

    and finally, the end of the dump extract of a windbg test on devenv.exe :

     

    ModLoad: 75d30000 75dc1000   C:\WINDOWS\system32\MLANG.dll
    (4d8.11f8): CLR exception - code e0434f4d (first chance)
    (4d8.11f8): CLR exception - code e0434f4d (first chance)
    (4d8.11f8): Access violation - code c0000005 (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=00000000 ebx=072a3f44 ecx=00a4d93c edx=00000000 esi=000000ea edi=00000000
    eip=597e88f2 esp=00105608 ebp=00105690 iopl=0         nv up ei pl nz na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010202
    msvb7!VBEditorFactory::CreateEditorInstance+0x695:
    597e88f2 8b08            mov     ecx,dword ptr [eax]  ds:0023:00000000=????????

     

    i already did uninstall-repair or reinstall several times without any luck...

     

    It still crashes...

     

    BTW :  when i boot win xp sp2 in SAFE MODE, the devenv work well and i can place my controls as i want, but it is safe mode (640x480)

     

    PLEASE HELP ME, I Can' work anymore...

     

    Thanks in advance.

     

    C.D.

     

    quinta-feira, 3 de maio de 2007 10:09
  • There could be a problem with the package, try running devenv.exe from the command line passing the /setup argument.
    quinta-feira, 3 de maio de 2007 10:59
  • thanks for the reply but i'm so fed up that i decided to follow (for the last time before reformatting xp) to clean VS2005 with the method explained here : http://support.microsoft.com/kb/907965/en-us

     

    i'm re-installing now...

     

    btw : i think that i already tried to use the "devenv /setup" and various options on the command line without success

     

    i'll tell you

    quinta-feira, 3 de maio de 2007 13:16
  • hi again,

     

    so now i installed vs2005 again (without service Pack), i rebooted, launched vs2005 shortcut, created a new winform project...

     

    and...when i right clicked on form1.vb to get design mode, crash again !!!!!!

     

    i tried devenv /setup, then restarted devenv

     

    same again, nothing changed...

     

    i'm gonna upgrade to sp1 now...

    quinta-feira, 3 de maio de 2007 14:03
  • also make sure that you install the latest updates from the Microsoft Update web site. If it crashes again you can start a second instance of Visual Studio, then attach to the first instance, reproduce the crash and create a dump file from the second Visual Studio 2005 instance. Then submit an issue report with the dump file on the Visual Studio 2005 Feedback web site.
    quinta-feira, 3 de maio de 2007 14:09
  • i had already a dump, i showed you the last words of this dump :

     

    eax=00000000 ebx=072a3f44 ecx=00a4d93c edx=00000000 esi=000000ea edi=00000000
    eip=597e88f2 esp=00105608 ebp=00105690 iopl=0         nv up ei pl nz na po nc
    cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010202
    msvb7!VBEditorFactory::CreateEditorInstance+0x695:
    597e88f2 8b08            mov     ecx,dword ptr [eax]  ds:0023:00000000=????????

     

    the offending DLL is msvb7.dll which can't createEditor Instance see above...

     

    i attached devenv to windbg as explained here :

     

    1. Install Debugging Tools for Windows. You can install them from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx (assuming you're running on an x86 machine; other platforms are also supported).
    2. Open a command prompt
    3. Change to the directory where you installed Debugging Tools for Windows
    4. Type in the following command:

    windbg -G -g D:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe (in quotes if necessary -- omit the angle brackets>
    5.This will run Visual Studio under WinDbg, which is a low-level debugger that is independent of Visual Studio (therefore, your ability to get us a minidump is not impacted by potential problems you’re seeing within VS).   


    6. When VS starts, run through the scenario that makes the problem happen. 
    7. At the point that you see the hang, do the following:

    a. Switch to WinDbg
    b. Hit Ctrl-Break. You should see some numbers (like “000:0”) appear in the lower left hand-corner of WinDbg. This is your signal that WinDbg is ready for your commands.
    c. In the textbox immediately to the right of the “000:0”, type in the following command exactly as shown and press Enter. This will instruct WinDbg to generate a minidump:

        .dump /o c:\dump.dmp


    8. At this point, you can exit WinDbg, which should also shut down Visual Studio. Copy the c:\dump.dmp file somewhere and email it to us. Please don't attach the minidump to the bug report, as it may contain information about your machine, directory structure, etc.

     

    do you want i upload the dump to you so can analize it ?

     

    See here, i posted but nobody can help !!!!

     

    https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=275208

     


    quinta-feira, 3 de maio de 2007 14:27
  • Sorry about that, I though that this was another thread. You say that you have reinstalled Visual Studio. Did you perform a repair installation or a full uninstall and a reinstall? Have you tried uninstalling and reinstalling the .NET Framework 2.0?
    quinta-feira, 3 de maio de 2007 15:16
  • today i did a full uninstall followed by reinstall (with custom choices C#, VB, WebDev, no crystal, noC++, no J++, no MSDN)

    followed by a SP1 install, followed by windows update...

    The framework 2.0 is automatically installed during vs install i guess !

    Last week, i made all kinds of uninstall/repair/and so on...no success

     

    Do i really need to unistall framework 2.0 and reinstall ????

     

    Thanks anyway.

    quinta-feira, 3 de maio de 2007 20:33
  • It is difficult to see what the prob is here but if you remove VS 2k5 it will not uninstall .NET Framework 2.0. Also this happens with an out of the box installation of Visual Studio? I mean you did not install anything on top of it or changed some settings? No anti-virus running, no virus on the system?

    quinta-feira, 3 de maio de 2007 20:54
  • when i uninstalled vs2k5, i also remove net 2.0, so i'm lost !!!

    i do have avast running ! mandatory nowadays, no ?

    something on top ? maybe but can't remember what.

     

    I regularly setup and unsetup stuffs found here and there, just trying utilities.

     

    do you think avast should be turned off when making installations ????

     

    good night, and see you tomorrow.

     

    I'm gonna sleep on this (it's 23h30 here in Belgium and you ? )

    quinta-feira, 3 de maio de 2007 21:34
  • Give it a try with the anti virus disabled. (I am in Belgium too and it is 1:30 when I post this :-p)

    quinta-feira, 3 de maio de 2007 23:28
  • oh Belgium too, so maybe you speak french ???

     

    I received a message from Connect.microsoft...

     

    "Generally it will be three months untill the PU team fix the bug."

     

    what a reply !!! they switched the case as "resolved", no hope for me i guess i'll have to rebuild all my ACER 9800 notebook with all software, all sp's, all everything or...stop using VS2k5 on it !!

     

    ***...

    sexta-feira, 4 de maio de 2007 08:10
  • one more thing, how can you explain that visual studio design view is working well when i boot my pc into safemode ???

    how could i compare what is loaded and what is not when in safemode under xp pro sp2 ?

     

     

    sexta-feira, 4 de maio de 2007 10:43
  • When you boot in safe mode only a subset of the device drivers are loaded (mouse, keyboard, microsoft vga driver ...) Since this is a gui related problem one could argue that the installed vga driver can cause this behaviour but as I said it is difficult to figure exactly out what goes wrong without knowing the internals of the modules. This is a trial and error approach, I would say try to uninstall your graphics drivers and try it again.

     

    By the way I live in the Flemish part of Belgium, namely Mechelen (Malines) in the lovely province named Antwerpen :-)

    sexta-feira, 4 de maio de 2007 11:19
  • i'm from Rochefort...

    i live in Ciney...

     

    Beer towns ;-)

     

    btw : my visual studio worked well during 6 month, i'm sure it's something else...

     

    i'm doing a parallel filemon on 2 PC to compare, i noticed that on the buggy machine, devenv .exe open msnmessenger ????

    is possible that after a devenv crash, the dw20 tries to communicate with ms support (send debug information) using msnmessenger agent ?


    14:26:41 devenv.exe:2072 OPEN C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Options: Open  Access: Read-Attributes 
    14:26:41 devenv.exe:2072 QUERY INFORMATION C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Attributes: A 
    14:26:41 devenv.exe:2072 CLOSE C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS  
    14:26:41 devenv.exe:2072 OPEN C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Options: Open  Access: 00100020 
    14:26:41 devenv.exe:2072 QUERY INFORMATION C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Length: 5674352 
    14:26:41 devenv.exe:2072 CLOSE C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS  
    14:26:41 devenv.exe:2072 OPEN C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Options: Open  Access: Read-Attributes 
    14:26:41 devenv.exe:2072 QUERY INFORMATION C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Attributes: A 
    14:26:41 devenv.exe:2072 CLOSE C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS  
    14:26:41 devenv.exe:2072 OPEN C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Options: Open  Access: Read 
    14:26:41 devenv.exe:2072 QUERY INFORMATION C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Length: 5674352 
    14:26:41 devenv.exe:2072 CLOSE C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS  
    14:26:41 devenv.exe:2072 OPEN C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Options: Open  Access: Read-Attributes 
    14:26:41 devenv.exe:2072 QUERY INFORMATION C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Attributes: A 
    14:26:41 devenv.exe:2072 CLOSE C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS  
    14:26:41 devenv.exe:2072 OPEN C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Options: Open  Access: 00100020 
    14:26:41 devenv.exe:2072 QUERY INFORMATION C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Length: 5674352 
    14:26:41 devenv.exe:2072 CLOSE C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS  
    14:26:41 devenv.exe:2072 OPEN C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Options: Open  Access: Read-Attributes 
    14:26:41 devenv.exe:2072 QUERY INFORMATION C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Attributes: A 
    14:26:41 devenv.exe:2072 CLOSE C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS  
    14:26:41 devenv.exe:2072 OPEN C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Options: Open  Access: Read 
    14:26:41 devenv.exe:2072 QUERY INFORMATION C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS Length: 5674352 
    14:26:41 devenv.exe:2072 CLOSE C:\Program Files\MSN Messenger\msnmsgr.exe SUCCESS  

     

    sexta-feira, 4 de maio de 2007 12:38
  • This is very odd. Did you install a Messenger Visual Studio add-in? Did you scan for spyware or viruses? I am unaware of such a feature that will reports bugs using the Messenger client.
    sexta-feira, 4 de maio de 2007 16:53
  • hi again,

     

     

    I made a big spyware and virus scan, removed some troubles but i'm still getting my problem with design view in VS2005 !!!

     

    Do you know somebody capable of dump analysis ?

     

    i made a more complete debug session with windbg but i am unable to decrypt where is the problem.

     

    thanks

     

    C.D.

    terça-feira, 8 de maio de 2007 12:14
  • I DON'T WANT TO THANK ALL THE DUMMIES WHO COULDN'T HELP ME DURING ALL THIS TIME.

    I WAS FED UP SO I REBUILDED MY XP2 AND AFTER 12 HOURS OF VARIOUS SETUPS UPDATES AND SO ON, MY VS2005 is ok !!!

     

     

    I WANT TO THANK Gabriel Lozano-Moran FOR HIS PATIENCE BUT...I WAS DESESPERATE

     

    GABRIEL , YOU ARE GREAT

    GABRIEL, JE BENT GROOT

    GABRIEL, TU ES SUPER

     

     

    quarta-feira, 9 de maio de 2007 21:39
  •  

    F81CD990-910B-4BBF-9CB3-6A77F3D697B3 - Is a DCOM permission error.  Did you check DCOM to be sure you have given msnmsgr.exe permission to run on your system?  It is possible you can set this from the policy manager but to simplify, did you check DCOM permissions on your msnmsgr?  Possibly there is a Windows Update tha disables the DCOM for F81CD990-910B-4BBF-9CB3-6A77F3D697B3 - the msgmsgr?   I am having issues also.  I'm not sure of the relationship but the server log indicates a DCOM Server is not running.   I vaguely remember turning this off when I first bought my computer.

    quinta-feira, 24 de julho de 2008 12:09
  • i have just installed vs2005 and have a problem with the design view of the IDE.  i cant place a button or txtbox or the like on the design view and see it.

    the code is there but it is invisible in design view. ive tried resetting all settings but with no look.

    is there a way to turn on the feature that allows for the display of buttons etc in design view.

     

    thanks

    jimkn

    Did you ever find the answer to this?  I use the vs for windows and in Mac and I can't even find the design view to add buttons etc for asp.net forms with c # app. 
    terça-feira, 17 de março de 2020 01:18