Handling .NET Exceptions in VB6


hi,

i have question regarding how vb6 handles exceptions raised .net component.

this scenario: have legacy vb6 app writing new functionality in managed assembly , accessing through com. in vb6 code used on error goto extensively , there places responding data access errors - kind come sqlserver stored procedure. specifially sp performs raiserror(50000,16,1) , vb6 code (inside error routine) handles err.number when 50000.

my .net component replaces direct call sp wanted keep vb6 code it, i.e. still responding err.number being 50000. problem seem have when .net component throws exception cannot err.number 50000. know if used comexception specify error code here error code must < 0 com error happen.

after that, guess need know if possible managed code raise vb6 error vb6 err.number positive?

thanks in advance

graham

hello graham,

sorry delay. wanted verify vb.net team :)

there breaking change made vb.net runtime whidbey (visual studio 2005) maintain compatibility vb6. clear, whidbey vb.net runtime break compatibility vb.net (everett 1.x), , return compatibility vb6.

if try code whidbey (which has not yet rtmd, betas available), should work expect.

if cannot wait or rely on vb.net whidbey, have option [in source code]. peek exception retrieve hresult , manually set error object:


dim c as new system.runtime.interopservices.comexception
err.number = c.errorcode
 


please feel free post forum if have questions or comments on issue.

hope helps,
stephen
http://blogs.msdn.com/stfisher



.NET Framework  >  Common Language Runtime Internals and Architecture



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