Visual Studio closes when I try to llok at project properties


if @ project's properties in visual studio 2008, right clicking on project , selecting properties, or selecting project main menu , selecting properties, visual studio closes.

this happens more 1 solution not @ time: have had happen 3 different solutions can @ properties of 1 caused vs close.

the application event viewer shows 3 errors in succession:


source=.net runtime time=15:40:24 category:none event id=1023
.net runtime version 2.0.50727.3053 - fatal execution engine error (7a035e00) (80131506)


source=.net runtime time=15:40:24 category:none event id=1023
.net runtime version 2.0.50727.3053 - fatal execution engine error (7a2e0f92) (0)


source=devenv time=15:41:03 category:none event id=0
description event id ( 0 ) in source ( devenv ) cannot found. local computer may not have necessary registry information or message dll files display messages remote computer. may able use /auxsource= flag retrieve description; see , support details. following information part of event: data source '{130bada6-e128-423c-9d07-02e4734d45d4}' specifies no supporting providers or set not registered..


any ideas?

andrew

sign of corrupt installation.  sign of bad plugin.  source control plugins have been known crash vs without warning.  svn known problem on.  using third-party plugins?

you should repair vs installation , rerun sp installer.  if project in question happen come source (such sql) rerun install instead.

if doesn't resolve problem it'll necessary stack trace ms can use diagnose problem.  1 step @ time though.

michael taylor - 10/7/08
http://p3net.mvps.org




Archived Forums V  >  Visual C# IDE



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more