VS 2008 crashes after opening a solution containing a web project


hi guys!

 

when try open solution team foundation server (2005) using vs team suite 2008, vs crashes. debugged bugger , discovered following error:

 

an unhandled exception of type 'system.stackoverflowexception' occurred in microsoft.visualstudio.shell.interop.dll

 

this problem not occur if team foundation client not installed , open same project. scenario however, produces logical error version control not found. that, expected.

 

i've opened connect issue (https://connect.microsoft.com/visualstudio/feedback/viewfeedback.aspx?feedbackid=331549), i'd know if here has had experience issue.

 

thanks in return,

 anže vodovnik

yes, have had at least 2 reports of identical stack traces.  there bug in web project system code discovered , fixed (internally).  fix expected go out in 2008 sp1.

 

for interested in fine details, web project code trying set web server port.  towards end calls queryedit indicate intent update file port number.  source control layer receives queryedit , tries determine if file changed under source control.  part of determination involves call isdocumentinproject see if ithe file part of bound project.  unfortunately, because of bug mentioned above, isdocumentinproject code in web project system goes through code senses needs update port number , again initiates queryedit.  loop , loop until blow stack.

 

one workaround unbind files source control have done.  possible workaround (i haven't tested this) might check out files using sce or tf.exe before opening solution.

 

--ben ryan



Archived Forums V  >  Team Foundation Server - Source and Version Control



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