VS2003编译器错误 [英] VS2003 Compiler Bug

问题描述

我不确定这是不是由visual studio或vb

编译器本身造成的错误。


我很好大小的解决方案（33个项目）和我一直有问题

有一个项目..


基本上每次我建立时，我得到编译器错误bc30456 .. .which

基本上没有声明一些局部变量。但是，变量是

声明...并且基本上如果我将其声明从私有更改为

protected项目将构建...但是下次我构建它将会失败......并且再次将其切换回私人构建。我也觉得它很奇怪，它在同一个项目中总是相同的变量。


希望有人可能之前见过这样的东西并且会认出

it。

谢谢

I''m not sure if this is a bug being caused by visual studio, or by the vb
compiler itself.

I have good size solution (33 projects) and am consistently having a problem
with one project..

Basically everytime I build, I get the compiler error bc30456...which is
basically that some local variable is not declared. However, the variable is
declared...and basically if I change its declaration from private to
protected the project will build...but then the next time I build it will
fail..and upon switching it back to private build again. I also find it
weird that it is always the same variable in the same project.

Hoping someone maybe has seen something like this before and will recognize
it.
Thanks

推荐答案

" chris" < CH **** @ nospam.nospam> schrieb：

"chris" <ch****@nospam.nospam> schrieb:

基本上每次构建时，我都会得到编译器错误bc30456 ......这基本上是没有声明某些局部变量。但是，变量
被声明...并且基本上如果我将其声明从私有更改为
受保护项目将构建...但是下次我构建它将会失败。 。再次将其切换回私人构建。我也觉得奇怪的是它在同一个项目中始终是同一个变量。

Basically everytime I build, I get the compiler error bc30456...which is
basically that some local variable is not declared. However, the variable
is declared...and basically if I change its declaration from private to
protected the project will build...but then the next time I build it will
fail..and upon switching it back to private build again. I also find it
weird that it is always the same variable in the same project.

Mhm ...那么，它是一个/ local / variable /或/变量at / type / level？


-

MS Herfried K. Wagner

MVP< URL ：http：//dotnet.mvps.org/>

VB< URL：http：//classicvb.org/petition/>

Mhm... So, is it a /local/ variable /or/ a variable at /type/ level?

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

这确实很奇怪，而且我非常希望我的团队能够调查 - 这听起来像编译器问题（与VS本身无关，但与VB编译器无关）。如果您导航到 http://lab.msdn.microsoft.com/productfeedback/ 并且会在那里提交报告，我真的很感激。它将收集我们需要的信息，然后在我们的数据库中生成报告。我们每天查看这些报告，它为我们提供了一种方式来向您提供有关我们进度的最新信息。


--Matt Gertz - *

VB编译器Dev Lead


-----原始消息-----

来自：chris

发布于：星期五， 2005年11月18日下午1:13

发布至：microsoft.public.dotnet.languages.vb

对话：VS2003编译器错误

主题：VS2003编译器错误

我不确定这是由visual studio或vb

编译器本身引起的错误。


我有一个很好的尺寸解决方案（33个项目）并且一直有问题

有一个项目..


基本上每次我建立，我得到编译器错误bc30456 ...这基本上是没有声明某些局部变量的b
。但是，变量是

声明...并且基本上如果我将其声明从私有更改为

protected项目将构建...但是下次我构建它将会失败......并且再次将其切换回私人构建。我也觉得它很奇怪，它在同一个项目中总是相同的变量。


希望有人可能之前见过这样的东西并且会认出

it。

谢谢

That is indeed weird, and something I''d very much like my team to investigate -- it sounds like a compiler problem (nothing to do with VS itself, but with the VB Compiler). If you navigate to http://lab.msdn.microsoft.com/productfeedback/ and would care to file a report there, I would really appreciate it. It will collect the information that we need from you, and then generate a report in our database. We look at those reports daily, and it gives us a way to give you updates on our progress.

--Matt Gertz--*
VB Compiler Dev Lead

-----Original Message-----
From: chris
Posted At: Friday, November 18, 2005 1:13 PM
Posted To: microsoft.public.dotnet.languages.vb
Conversation: VS2003 Compiler Bug
Subject: VS2003 Compiler Bug
I''m not sure if this is a bug being caused by visual studio, or by the vb
compiler itself.

I have good size solution (33 projects) and am consistently having a problem
with one project..

Basically everytime I build, I get the compiler error bc30456...which is
basically that some local variable is not declared. However, the variable is
declared...and basically if I change its declaration from private to
protected the project will build...but then the next time I build it will
fail..and upon switching it back to private build again. I also find it
weird that it is always the same variable in the same project.

Hoping someone maybe has seen something like this before and will recognize
it.
Thanks

（哦，在这种情况下忽略你使用2003的事实而不是2005年，这是MSDN反馈中心在技术上的目标。我想确保这在2005年和2003年都不会引起反响。）

(Oh, and ignore the fact in this case that you''re using 2003 instead of 2005, which is what the MSDN Feedback center is technically targeted for. I want to make sure that this isn''t reproing in 2005 as well as 2003.)

这篇关于VS2003编译器错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！