Error - PlatformVerificationTask

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Ok, so I copied a CF V1.0 project that had worked well and passed testing
into a new directory and opened in VS 2005 Professional. It automatically
converted to VS 2005. In addition, I right clicked on the project and
converted it from CF 1.0 to 2.0. I just started getting the following warning
on compilation (question continues after error)...


An internal error occurred in PlatformVerificationTask.
System.Runtime.InteropServices.COMException (0x8000000A): The data necessary
to complete this operation is not yet available. (Exception from HRESULT:
0x8000000A)
at System.Reflection.Assembly.GetType(String name, Boolean throwOnError,
Boolean ignoreCase)
at System.Reflection.Assembly.GetType(String name)
at Microsoft.CompactFramework.Build.MetadataService.GetAsmmetaType(Type
sourceType)
at
Microsoft.CompactFramework.Build.MetadataService.GetTypeAttributes(String
instanceType)
at
Microsoft.CompactFramework.Build.Tasks.PlatformVerificationRule.VisitConstruct(Construct cons)
at Microsoft.CompactFramework.Build.Compiler.StandardVisitor.Visit(Node
node)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitExpression(Expression expression)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitAssignmentStatement(AssignmentStatement assignment)
at Microsoft.CompactFramework.Build.Compiler.StandardVisitor.Visit(Node
node)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitStatementList(StatementList statements)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitBlock(Block
block)
at Microsoft.CompactFramework.Build.Compiler.StandardVisitor.Visit(Node
node)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitStatementList(StatementList statements)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitBlock(Block
block)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitMethod(Method
method)
at Microsoft.CompactFramework.Build.Compiler.StandardVisitor.Visit(Node
node)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitMemberList(MemberList members)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitTypeNode(TypeNode typeNode)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitClass(Class
Class)
at Microsoft.CompactFramework.Build.Compiler.StandardVisitor.Visit(Node
node)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitTypeNodeList(TypeNodeList types)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitModule(Module
module)
at
Microsoft.CompactFramework.Build.Compiler.StandardVisitor.VisitAssembly(AssemblyNode assembly)
at
Microsoft.CompactFramework.Build.Tasks.PlatformVerificationTask.Execute() PreProcEval



Additionally, if I attempt to debug the app in spite of the warning, the
breakpoints disable and produce the following message: "The breakpoint will
not currently be hit. No symbols have been loaded for this document."

When I attemp to shut down the debugger I get a dialog with the following
message; "No symbols have been loaded for any stack frame. The source code
cannot be displayed." This is immediately followed by a
NullReferenceException;

System.NullReferenceException was unhandled

Message="NullReferenceException"
StackTrace:
at PreProcEval.StartPreProc.LoadScreen()
at PreProcEval.StartPreProc.StartPreProc_Load()
at System.Windows.Forms.Form.OnLoad()
at System.Windows.Forms.Form._SetVisibleNotify()
at System.Windows.Forms.Control.set_Visible()
at System.Windows.Forms.Application.Run()
at PreProcEval.StartPreProc.Main()"

Does anyone have the first clue as to what is going on here?

Bill
.



Relevant Pages

  • Re: need help on need help on generator...
    ... I'm not dumb enough to say "Sure, ... I'd be happier to change the behaviour so that a warning isn't ... so long as nobody is relying on the ... read over the `file' source code before impulsively saying anything ...
    (comp.lang.python)
  • Re: regcmp warning: improper pointer/integer combination: op "="
    ... without the source code one can only guess. ... Here we deal with standard C not extensions provided by specific ... compiler warning. ...
    (comp.lang.c)
  • Re: Arithmetic conversions and integer constants
    ... source code cannot fit in any integer type the implementation ... Is the compiler obliged to give a warning ... because the constraint in p2 of 6.4.4 was violated? ...
    (comp.lang.c)
  • Re: not all paths return a value
    ... any boolean function/variable/whatever, explicitly setting the return = False should never be required. ... If it is suddenly required after 30 years of programming, there should be a huge notice posted on the web somewhere that says "forget about your existing source code, everything has suddenly changed for no good reason" ... My main concern is that the warning only occurs at functions which return a reference type. ...
    (microsoft.public.dotnet.languages.vb)