Error 1 Project-level Conditional Compilation Constant
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up VB Compiler Error(No Clue) up vote 0 down vote favorite Okay i keep getting this error and i have done all there is to do but it just wouldn't go. Can anyone give me any idea please? Project-level conditional compilation constant 'VBC_VER = 9.0, TARGET = "winexe", CONFIG= "Debug", PLATFORM= "x86" , DEBUG; ^^ ^^ TRACE' is not valid: Character is not valid vb.net visual-studio share|improve this question edited Mar 5 '12 at 16:08 Joel Coehoorn 248k92440661 asked Mar 5 '12 at 6:41 C'est Moi 161 Wild guess: put 9.0 in quotes? –Ian Horwill Mar 5 '12 at 17:04 add a comment| 5 Answers 5 active oldest votes up vote 0 down vote You have set a conditional compilation constant that contains an invalid character. Check your project properties. share|improve this answer answered Mar 5 '12 at 6:46 Andrei G 1,464512 I don't seem to see anything on there.Am so clueless on this particular issue. –C'est Moi Mar 5 '12 at 16:10 add a comment| up vote 0 down vote I would say one of those conditions has a syntax error. though I don't know which. Could it be win.exe instead of winexe? share|improve this answer answered Mar 5 '12 at 10:34 Aeropher 77312 Should i change it to win.exe? Sorry am pretty new at this so i don't know much about properties. –C'est Moi Mar 5 '12 at 16:11 I don't know what's going wrong other than it's a syntax error. so I'd try it out
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and http://stackoverflow.com/questions/9562598/vb-compiler-errorno-clue Languages Mobile and Embedded Development .NET Development Office development Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. https://msdn.microsoft.com/en-us/library/5yh6f4ww.aspx This documentation is archived and is not being maintained. Project-level conditional compilation constant ' Issues » Cannot build VB.Net projects. Get error vbc, NCRUNCH; ^^ ^^ ' is not valid: Character is not valid. Cannot build VB.Net projects. Get error vbc, NCRUNCH; http://forum.ncrunch.net/yaf_postst195_Cannot-build-VB-Net-projects--Get-error-vbc--NCRUNCH-------is-not-valid--Character-is-not-valid.aspx ^^ ^^ ' is not valid: Character is not valid. http://dailydoseofexcel.com/archives/2006/02/16/conditional-compilation-arguments/ Options Previous Topic Next Topic mg_steele #1 Posted : Monday, February 06, 2012 12:29:44 PM(UTC) Rank: NewbieGroups: Registered Joined: 2/4/2012(UTC)Posts: 4Location: UKWas thanked: 1 time(s) in 1 post(s) The latest version of Ncrunch 1.37.0. 46.b fails to build my VB.Net projects. They ran error 1 ok in the last version.The error I am getting isvbc (0): Project-level conditional compilation constant 'VBC_VER = 9.0,TARGET = "library",CONFIG="Debug",DEBUG=-1,TRACE=-1,_MyType="Windows",PLATFORM="AnyCPU",NCRUNCH; ^^ ^^ ' is not valid: Character is not valid.When I remove any van Gelder in Uncategorized on February 16, 2006. When I first started programming for Excel, I decided it would be a good idea to standardise on a method for switching between Production mode and Testing mode. You know, so you save face after your code just failed to build the where clause into a delete query. I'd seen a few approaches but I eventually settled on a Public Const in the first module of the workbook. However, I've just discovered another way to switch between Production and Test modes: Conditional Compilation Arguments I think if I had the choice again, this is the way I'd have chosen. You get to them from the Visual Basic Editor menu: Tools - VBAProject Properties… Usually that's VBAProject Properties, but will be whatever you've named your project. You can also get to the same window by right-clicking the Project from the Project Explorer pane. The Project Properties window appears… The last textbox of the General tab is Conditional Compilation Arguments This is where you put your Compiler Constants. They behave just like #Const constants. They will save when your save the Workbook. You can enter more than 1 argument by separating them with a colon : So your VBA code could look as follows: Sub MyCode() #If TestMode Then MsgBox "This is Test Mode", vbExclamation #Else MsgBox "This is Production Mode", vbInformation #End If #If Not AdministratorMode Then InputBox "What's the password?" #End If End Sub I'm interested in your feedback - please post a comment. How do you separate Production from Test? By Rob van Gelder in Uncategorized on February 16, 2006. 17 Replies Post navigation ← Hyperlinks and Network Shares Printing Fit to Page Width → 17 thoughts on “Conditional Compilation Arguments” Stephen Bullen February 16, 2006 at 4:24 am I often use a registry entry, so if I'm at a user's desk, I can flip a registry setting and get much more information, developer-related error messages, less on-sheet protection, shortcut keys to access the VBProject etc. XL-Dennis February 16, 2006 at 10:18 am Rob, In addition to Stephen's approach I also use textfiles to track and log on user's computers (and network). This is valuable when the engagements are on a ‘remote' work as the files are easy to mail. Keep up the good work Rob :) Kind Regards, Dennis mschaef February 16, 2006 at 10:48 am C programmers have been struggling with this for 30 years. C++ and Java were actually designed to make it possible to avoid conditional compilation. Here's why: Public Sub hello(