|
| broken Visual Studio 2003 |
|
|
|
|
| Messages |
|
Related Types |
This message was discovered on microsoft.public.vsnet.setup.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.
| BillA |
| GOOD ANSWER |
I have a broken Visual Studio 2003 app. On the start page the modified date for the projects does not update, in a project(solution) the Web Form Designer generated code is throwing an error, when a breakpoint is set on a specific line and then the project is run in debug mode the breakpoint has been shifted to an unrelated line of code.
I have a RequiredFieldValidator control on this page that is not even referencing the correct button and preventing me from finishing the debugging of the page's code. I removed the RequiredFieldValidator control and replaced it but it is still not responding correctly.
Additionally, yesterday the entire program closed abruptly and completely on its own. After that I "repaired" VS.NET 2003 and at least it is not crashing but all of the other symptoms are still there.
I have also downloaded and reinstalled the .Net Framework SDK 1.1 to no avail.
Any suggestions, thoughts, ideas would be greatly appreciated.
Regards,
Bill Antonacchio
|
|
|
| |
|
|
| |
| |
| Mark Smith [MSFT] (VIP) |
Bill,
The problem you are experiencing is often times caused by interference
during Installation by 3rd Party Software, such as your Antivirus client or
possibly a personal Firewall. It can also be caused by different types of
file corruption. This corruption can be caused with problems in the file
system, Antivirus "cleaning" procedures, and other various issues. The
solution involves performing a modified repair operation on both the .NET
Framework 1.1 and your Visual Studio .NET 2003. Please refer to the
following steps to repair your Installation:
Enable Verbose Logging
1. Click Start>Run
2. Enter “regedit” without the quotes
3. Browse to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows
4. Right Click on the Installer key in the left pane and choose
New>String value
5. Set the String>value name to Logging
6. Double click logging and change the Value data to “voicewarmup”
without the quotes
7. Close the Registry Editor
8. To reverse this process at any time, delete the Logging String
value
Perform Diagnostic Boot:
1. Click Start>Run
2. Enter "msconfig" without the quotes (if you use GoBack, please
stop at this point and contact me directly)
3. Select Diagnostic Startup
4. Click Service tab and check the box next to Windows Installer
5. Hit OK and Restart Windows
Clear Temp Directory:
1. Click Start>Run
2. Enter "%temp%" without the quotes
3. Hit Control-A to select all and hit Delete to send all the files
to the recycle bin
Perform Repair Installation of the .NET Framework 1.1
1. Insert your Visual Studio .NET 2003 Professional Prerequisites
disk
2. Cancel any dialog boxes that appear (Choose Yes to run setup from
Disk 1)
3. Click Start>Run
4. Enter "x:\dotnetframework\dotnetfx.exe" /t:c:\windows\temp
/c:"msiexec.exe /i c:\windows\temp\netfx.msi REINSTALL=ALL
REINSTALLMODE=vacmus" (maintain all quotes and replace x:\dotnetframework
with the path to dotnetfx.exe on your Prerequisites CDROM. If necessary,
use Search function to find the correct path to dotnetfx.exe)
Perform Repair Installation of Visual Studio .NET 2003 Professional
1. Insert your Visual Studio .NET 2003 Professional Setup Disk 1
2. Cancel any dialog boxes that appear
3. Click Start>Run
4. Enter "x:\vs_setup.msi" REINSTALL=ALL REINSTALLMODE=vacmus
(Change x: to your CDROM drive letter)
In the Event of Failure
1. Click Start>Run
2. Enter "%temp%" without the quotes
3. Select any LOG or TXT files (identifiable by Notepad icon)
4. Use compression utility (WinZip, WinRAR, etc) to zip the files
5. Reply to this message and attach log files for review
Thank you for using Microsoft Developer Support
Mark Smith, Microsoft Developer Support, Setup & Deployment
Support Engineer, Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
| |
|
|
| |
| |
| Paul McKee [MSFT] (VIP) |
Bill,
I hope these steps restored proper operation of Visual Studio .NET 2003 on
your system. I just wanted to respond to the very first issue listed in
your message: "On the start page the modified date for the projects does
not update."
Visual Studio .NET 2003 uses the date of the .sln file as the Modified date
in the Start Page, so that if the .sln file is not modified, the date shown
in the Start Page does not change. The .sln file is modified when you add
or remove projects, change solution options, change project dependencies,
etc. Just opening a solution and working on your code, for example,
doesn't update the .sln file.
(Back in Visual Studio .NET 2002, the last modified date of the .suo file
in the solution folder (it is a hidden file) was used. Since this .suo
file is used to persist options you set in the IDE, IDE updates it when you
close the solution.)
I'm working on this area for the next release if you have any further
comments about this.
Thanks!
Paul McKee
VS Core team
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
| |
|
|
| |
| |
| Peter van der Goes |
"Paul McKee [MSFT]" <Click here to reveal e-mail address> wrote in message
news:Click here to reveal e-mail address...
[Original message clipped]
I'll take the offered opportunity to comment.
I believe that most developers would consider any change to a solution,
including a simple code fix, an update. I would like to see a return to the
VS.Net 2002 way of doing things.
--
Peter [MVP Visual Developer]
Jack of all trades, master of none.
|
|
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
BootFX
Reliable and powerful .NET application framework. |
|
|
|
|
|
|
