Thanks for your followup MrSpock,
So far I haven't any other ideas on this. If possible I'd suggest you
rebuild a clean XP environment for testing... Most likely such problem is
a environment specific issue...
regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
| Thread-Topic: VS2005: "Make single instance application"
| thread-index: AcX2TK1NtbqTCUhnTquYEPksmEifVA==
| X-WBNR-Posting-Host: 62.181.97.149
| From: "=?Utf-8?B?TXJTcG9jaw==?=" <
[email protected]>
| References: <
[email protected]>
<eknofD#
[email protected]>
<
[email protected]>
<#
[email protected]>
<
[email protected]>
| Subject: RE: VS2005: "Make single instance application"
| Date: Wed, 30 Nov 2005 23:56:03 -0800
| Lines: 86
| Message-ID: <
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.dotnet.languages.vb
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.dotnet.languages.vb:306689
| X-Tomcat-NG: microsoft.public.dotnet.languages.vb
|
| Mr Cheng,
|
| Thanks for your efforts! I will have to use some other solution for the
| single instance feature in my applications, but it would be nice to know
the
| cause to this error though.
|
| Best regards,
|
| MrSpock
|
|
| "Steven Cheng[MSFT]" wrote:
|
| > Hi MrSpock,
| >
| > After some further tests on my local XP environment, I think this
should be
| > a envionement specific problem since a typical VB.NET winform app with
| > single instance flag turned on can run correctly on XP box.
| >
| > Thanks,
| >
| > Steven Cheng
| > Microsoft Online Support
| >
| > |
| > | Thanks for your response MrSpock,
| > |
| > | I don't think this will be a existing or by design behavior for XP
| > | platform.. I'll try perform some further test in my local
envionrment
| > and
| > | let you know my result soon.
| > |
| > | Regards,
| > |
| > | Steven Cheng
| > | Microsoft Online Support
| > |
| > | |
| > | | Thanks for your answer, Mr Cheng.
| > | |
| > | | My first test was performed on WinXP SP2 with .NET 2.0.
| > | |
| > | | Today I did a clean install of VS2005 on another dev box (WinXP
SP2,
| > .NET
| > | | 2.0). I got the same error this time!
| > | |
| > | | Later I copied the same executable to another box running Win2k3.
No
| > | errors
| > | | this time!
| > | |
| > | | I suppose the "single instance" option isn't fully functional on
WinXP,
| > | right?
| > | |
| > | | Best regards,
| > | |
| > | | MrSpock
| > | |
| > | |
| > | | "Steven Cheng[MSFT]" wrote:
| > | |
| > | | > Hi MrSpock,
| > | | >
| > | | > Regarding on the VB.NET single instance winform application
problem,
| > | I've
| > | | > just performed some tests on my local side(win2k3server .net 2.0
| > | vs2005),
| > | | > seems I can not reproduce the
| > | | > ===========
| > | | > Debug info: "Unhandled exception at 0x00e149fd in
| > | WindowsApplication1.exe:
| > | | > 0xC0000005: Access violation writing location 0x00000000."
| > | | > ===========
| > | | >
| > | | > error by try launching the winform app(exe) multiple times. I'm
not
| > | sure
| > | | > whether there're any other particular steps when you reproduce
this
| > | | > behavor? My test winform is just a simple application with a
empty
| > | form in
| > | | > it. In addition, have you tried this on some other dev box to
see
| > | whether
| > | | > you also encounter this error?
| > | | >
| > | | > Thanks,
| > | | >
| > | | > Steven Cheng
| > | | > Microsoft Online Support
|
