Hi David,

You will need to break this down, as there isn't enough detail to go on
here.

Some questions:

Is this a web service?  
Have you tried to place a break-point in the method that you think is
failing?
Is this failing when you compile it?  Or when you call it?
Can you start the service in debug mode (e.g. debug/start with debugging)?  
Do you get the automatic document page?  Or does the error occur right here.

If it occurs immediately, there is an issue in the construction of the
class.  This can be caused by bad code in your constructor, or by any logic
called by the constructor.

Some thoughts

Dan Rogers
Microsoft Corporation
--------------------
Thread-Topic: Parser Error - Could not create type?
thread-index: AcTIHAlGSTv9tvXnSSaOPHFYgaMk4g==
X-WBNR-Posting-Host: 204.96.22.25
From: "=?Utf-8?B?ZG90TmV0RGF2ZQ==?=" <dotNetDave@discussions.microsoft.com>
Subject: Parser Error - Could not create type?
Date: Thu, 11 Nov 2004 10:27:01 -0800
Lines: 23
Message-ID: <AAF7FCC2-6E39-4BF4-9F9E-DF173DD6794A@microsoft.com>
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.framework.webservices
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7379
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices

I keep getting the following error on one of my web service pages:

Parser Error
Parser Error Message: Could not create type
'SyPixx.Web.ClearService.ConfigureAlarms'.

Source Error:
Line 1:  <%@ WebService Language="vb" Codebehind="ConfigureAlarms.asmx.vb"
Class="SyPixx.Web.ClearService.ConfigureAlarms" %>

Currently I can't get past this. In the past if I rebuilt my application it
would go away then reapear on the same asmx page or a different one or even
the  global.asax page. This can happen while running the asmx page in
VS.NET
debugging or with IE. Does not seem to matter.

I thought something was wrong with VS.NET or my machine so I rebuilt my
machine, reinstalled VS.NET and it keeps happening.

Anyone have any ideas?

=====================
David McCarter
www.vsdntips.com