Hi Jeffery,
Did you ever get a response to this? I and several other engineers at
my company have had the same problem. The only way we've been able to
work-around is to completely reinstall VS.
[Yes, error messages would be nice, wouldn't they? If Microsoft had
programmed the HAL 9000 computer in 2001: A Space Oddessy, it would
never had explained *why* is wouldn't open the pod bay doors, it would
just grey out the button or say "access denied; contact your system
administrator".]
[quoted text, click to view] Jeffrey Huntsman wrote:
> OK, I decided to pursue this using another instance of the VS.NET Debugger
> and actually try and debug the process. I found out that the root cause of
> this was an exception being thrown when the designer tried to instantiate an
> instance of the form's base class. The exhibited behavior (no properties)
> certainly did not lend even a clue as to the cause of the problem.
>
> HOW ABOUT SOME ERROR
> MESSAGES!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
>
>
> "Jeffrey Huntsman" <jhuntsman@__oakwoodsys_com> wrote in message
> news:OcpKZ0bnDHA.1672@TK2MSFTNGP09.phx.gbl...
>
>>This started happening to me this morning. Since then, I have done the
>>following to no avail:
>>
>>1. Repair VS.NET 2003 EA
>>2. Repair .NET Framework 1.1
>>3. Uninstall VS.NET 2003 EA
>>4. Reinstall VS.NET 2003 EA
>>
>>Nothing has worked. Visual Studio is practically unusable without being
>>
> able
>
>>to see ANY properties for a selected object.
>>
>>Does anyone know of a possible solution for this???
>>
>>Thanks,
>>
>>Jeffrey
>>
>>
>>
>
>
Hi Jeffery,
Did you ever get a response to this? I and several other engineers at
my company have had the same problem. The only way we've been able to
work-around is to completely reinstall VS.
[Yes, error messages would be nice, wouldn't they? If Microsoft had
programmed the HAL 9000 computer in 2001: A Space Oddessy, it would
never had explained *why* is wouldn't open the pod bay doors, it would
just grey out the button or say "access denied; contact your system
administrator".]
[quoted text, click to view] Jeffrey Huntsman wrote:
> OK, I decided to pursue this using another instance of the VS.NET Debugger
> and actually try and debug the process. I found out that the root cause of
> this was an exception being thrown when the designer tried to instantiate an
> instance of the form's base class. The exhibited behavior (no properties)
> certainly did not lend even a clue as to the cause of the problem.
>
> HOW ABOUT SOME ERROR
> MESSAGES!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
>
>
> "Jeffrey Huntsman" <jhuntsman@__oakwoodsys_com> wrote in message
> news:OcpKZ0bnDHA.1672@TK2MSFTNGP09.phx.gbl...
>
>>This started happening to me this morning. Since then, I have done the
>>following to no avail:
>>
>>1. Repair VS.NET 2003 EA
>>2. Repair .NET Framework 1.1
>>3. Uninstall VS.NET 2003 EA
>>4. Reinstall VS.NET 2003 EA
>>
>>Nothing has worked. Visual Studio is practically unusable without being
>>
> able
>
>>to see ANY properties for a selected object.
>>
>>Does anyone know of a possible solution for this???
>>
>>Thanks,
>>
>>Jeffrey
>>
>>
>>
>
>
Hi Jeffery,
Did you ever get a response to this? I and several other engineers at
my company have had the same problem. The only way we've been able to
work-around is to completely reinstall VS.
[Yes, error messages would be nice, wouldn't they? If Microsoft had
programmed the HAL 9000 computer in 2001: A Space Oddessy, it would
never had explained *why* is wouldn't open the pod bay doors, it would
just grey out the button or say "access denied; contact your system
administrator".]
[quoted text, click to view] Jeffrey Huntsman wrote:
> OK, I decided to pursue this using another instance of the VS.NET Debugger
> and actually try and debug the process. I found out that the root cause of
> this was an exception being thrown when the designer tried to instantiate an
> instance of the form's base class. The exhibited behavior (no properties)
> certainly did not lend even a clue as to the cause of the problem.
>
> HOW ABOUT SOME ERROR
> MESSAGES!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
>
>
> "Jeffrey Huntsman" <jhuntsman@__oakwoodsys_com> wrote in message
> news:OcpKZ0bnDHA.1672@TK2MSFTNGP09.phx.gbl...
>
>>This started happening to me this morning. Since then, I have done the
>>following to no avail:
>>
>>1. Repair VS.NET 2003 EA
>>2. Repair .NET Framework 1.1
>>3. Uninstall VS.NET 2003 EA
>>4. Reinstall VS.NET 2003 EA
>>
>>Nothing has worked. Visual Studio is practically unusable without being
>>
> able
>
>>to see ANY properties for a selected object.
>>
>>Does anyone know of a possible solution for this???
>>
>>Thanks,
>>
>>Jeffrey
>>
>>
>>
>
>
Don't see what you're looking for? Try a search.
