Before I start peppering this forum with questions I'll start with one that might help me figure out others...
I'm trying to debug a custom component I'm developing. All the texts I've read state that the first thing I should do is attach to the devenv.exe process. When I choose this, the window that lists the available processes I can attach to does not contain devenv.exe.
Is this a security issue Any other ideas I'm an administrator on the box. Most of my career's been spent in UNIX environments, so perhaps I'm missing something basic I'm unaware of.
Thanks.
Unable to attach to devenv.exe to debug
Hot Topic
- Optional command line parameter
- SQL 2005 Agent Configuration issues
- problem regarding relationship
- DataReader Source and ODBC connection to PostgresSQL
- Gettint error "product level is insufficient" - did full re-install of SQL 2005 Standard Edition
- Importing Crystal Reports 9 reports into Reporting Services 2005
- Error at Transfer Objects Task: The source server can not be the same as the destination server.
- variables in sql command
- How to get the SessionID from the html viewer?
- Import/Export data with SQL Server 2005 Express
SQL Server
- Can't get Connection String to work in File Connection Manager
- SQL Configuration holding connections to DS
- Persistent BI Studio Crashes
- Export to Excel - Multiple Columns
- Database group
- Query performance
- SQL Express: Deploy reports on customer side
- a generic error occurred in gdi+
- Reporting services and VBCrlf
- Limit Report Server Access
Unable to attach to devenv.exe to debug
A_M
Austin Ehlers
Do you have another instance of VS (or BIDS) open in which you are using your custom component That is the process that you need to connect to.
-Jamie