Fatal Error C1192 #using
Contents |
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 fatal error c1113: #using failed on content you requested has been removed. You’ll be auto redirected in 1 second.
C1113 Nissan Xterra
C/C++ Building Reference C/C++ Build Errors Compiler Fatal Errors C999 through C1999 Compiler Fatal Errors C999 through C1999 Fatal Error C1192 Fatal Error C1192 Fatal Error C1192 Fatal Error C999 Fatal Error C1001 Fatal Error C1002 Fatal Error C1003 Fatal Error C1004 Fatal Error C1005 Fatal Error C1007 Fatal Error C1008 Fatal Error C1009 Fatal Error C1010 Fatal Error C1012 Fatal Error C1013 Fatal Error C1014 Fatal Error C1016 Fatal Error C1017 Fatal Error C1018 Fatal Error C1019 Fatal Error C1020 Fatal Error C1021 Fatal Error C1022 Fatal Error C1023 Fatal Error C1026 Fatal Error C1033 Fatal Error C1035 Fatal Error C1037 Fatal Error C1038 Fatal Error C1045 Fatal Error C1046 Fatal Error C1047 Fatal Error C1051 Fatal Error C1053 Fatal Error C1054 Fatal Error C1055 Fatal Error C1057 Fatal Error C1060 Fatal Error C1061 Fatal Error C1064 Fatal Error C1065 Fatal Error C1067 Fatal Error C1068 Fatal Error C1070 Fatal Error C1071 Fatal Error C1073 Fatal Error C1074 Fatal Error C1075 Fatal Error C1076 Fatal Error C1077 Fatal Error C1079 Fatal Error C1080 Fatal Error C1081 Fatal Error C1082 Fatal Error C1083 Fatal Error C1084 Fatal Error C1085 Fatal Error C1086 Fatal Error C1087 Fatal Error C1088 Fatal Error C1089 Fatal Error C1091 Fatal Error C1092 Fatal Error C1093 Fatal Error C1094 Fatal Error C1098 Fatal Error C1099 Fatal Error C1100 Fatal Error C1103 Fatal Error C1104 Fatal Error C1107 Fatal Error C1108 Fatal Error C1109 Fatal Error C1113 Fatal Error C1120 Fatal Error C1121 Fatal Error C1126 Fatal Error C1128 Fatal Error C1189 Fatal Error C1190 Fatal Error C1191 Fatal Error C1192 Fatal Error C1196 Fatal Error C1197 Fatal Error C1201 Fatal Error C1202 Fatal Error C1205 Fatal Error C1206 Fatal Error C1207 Fatal Error C1208 Fatal Error C1209 Fatal Error C1210 Fatal Error C1211 Fatal Error C1305 Fatal Error C1307 Fatal Error C1308 Fatal Error C1309 Fatal Error C1310 Fatal Error C1311 Fatal Error C1312 Fatal Error C1313 Fatal Error C1350 Fatal Error C1351 Fatal Error C1352 Fatal Error C135
Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question View Unanswered Questions View All Questions... C# questions Linux questions ASP.NET questions SQL questions VB.NET questions discussionsforums All Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work Issues Design and Architecture ASP.NET JavaScript C / C++ / MFC> ATL / WTL / STL Managed C++/CLI C# Free Tools Objective-C and Swift Database Hardware & Devices> https://msdn.microsoft.com/en-us/library/z2ky5tfk.aspx System Admin Hosting and Servers Java .NET Framework Android iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and Abuse Watch features Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff communitylounge Who's Who Most Valuable Professionals The Lounge The Insider News The http://www.codeproject.com/Messages/1802050/fatal-error-C1192-sharpusing-failed-on-c-compressi.aspx Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising Employment Opportunities About Us Home » Discussions » C / C++ / MFC Feature Forums- Uncategorised posts - General Programming.NET Framework Algorithms ATL / WTL / STL C / C++ / MFC C# COM Delphi Design and Architecture Graphics Hardware & Devices Java LINQ Managed C++/CLI Objective-C and Swift Regular Expressions Silverlight / WPF Visual Basic Visual Studio Visual Studio 2015 & .NET 4.6 WCF and WF Windows 10, 8, and RT Windows API Windows Forms XML / XSL Web DevelopmentASP.NET Cloud Computing JavaScript Linux, Apache, MySQL, PHP SharePoint Web Development Mobile DevelopmentAndroid iOS Mobile Product LifecycleApplication Lifecycle Collaboration / Beta Testing Free Tools Running a Business Sales / Marketing Database & SysAdminDatabase Hosting and Servers System Admin General DiscussionsArticle Writing Buzzword Bingo CodeProject API Get-Togethers Press Releases Site Bugs / Suggestions
help? Post your question and get tips & solutions from a community of 418,550 IT Pros & Developers. It's quick & easy. C++ debug/release builds and project references P: n/a https://bytes.com/topic/net/answers/595867-c-debug-release-builds-project-references Andrew Rowley I am having trouble getting debug and release builds to work properly http://microsoft.public.vsnet.ide.narkive.com/A9Z31UIF/mixed-up-configurations-when-building with project references using C++ .NET and Visual Studio 2003. I created a test solution, with a basic Windows form C++ project. I then add a class library, and add a reference to this project in the first project. When I do a release build, I see the following in the output from the DLL compile: fatal error /OUT:"C:\Documents and Settings\Andrew\My Documents\Visual Studio Projects\DependencyTest\Release\test.dll" OK so far. When the windows form app compiles, however, I see: /FU "c:\Documents and Settings\Andrew\My Documents\Visual Studio Projects\DependencyTest\Debug\test.dll" Where does this "Debug" come from? Everywhere else in the output says "Release". Can anyone tell me what I am doing wrong? How can I use a debug version of a DLL for a debug build, and a release version for the release build? fatal error c1192 -- Andrew Rowley Feb 1 '07 #1 Post Reply Share this Question 6 Replies P: n/a =?Utf-8?B?QnJ1bm8gdmFuIERvb3JlbiBbTVZQIFZDKytd?= I am having trouble getting debug and release builds to work properly with project references using C++ .NET and Visual Studio 2003. I created a test solution, with a basic Windows form C++ project. I then add a class library, and add a reference to this project in the first project. When I do a release build, I see the following in the output from the DLL compile: /OUT:"C:\Documents and Settings\Andrew\My Documents\Visual Studio Projects\DependencyTest\Release\test.dll" OK so far. When the windows form app compiles, however, I see: /FU "c:\Documents and Settings\Andrew\My Documents\Visual Studio Projects\DependencyTest\Debug\test.dll" Where does this "Debug" come from? Everywhere else in the output says "Release". Can anyone tell me what I am doing wrong? How can I use a debug version of a DLL for a debug build, and a release version for the release build? Hi, How did you add the reference? Did you select the DLL by browsing to it, or did your use the 'projects' tab in the references dialog? Also, if you open build->configuration manager you can see how the debug / release builds are configured. It could be possible that your solution release config
a C# class library project (name Lib,defining a class Lib.Fred), and also a managed C++ class library project(name Imp, defining a class which inherits from Lib::Fred). Imp'sreferences include a reference to the project Lib (i.e. the C++ refersto the C#).If I open the solution, choose the Release configuration, and press"Build Solution", the C# project compiles normally but then the managedC++ project build fails, apparently trying to refer the the /Debug/configuration of the C# project.If, instead, I open the solution, choose the Release configuration asbefore, and then close and reopen the solution before pressing build,the compilation succeeds.So far this is irritating, but not a serious problem. What does cause mereal difficulty is if I try to do a command-line build instead of usingthe IDE. This fails in an apparently different manner, and I have foundno workround. This is preventing automated product builds from running.I'd really appreciate a fix, workround, or pointer to where I'm beingstupid!The messages from a failed interactive build...------ Build started: Project: Lib, Configuration: Release .NET ------Preparing resources...Updating references...Performing main compilation...Build complete -- 0 errors, 0 warningsBuilding satellite assemblies...------ Build started: Project: Imp, Configuration: Release Win32 ------Compiling...Stdafx.cppStdafx.cpp(0) : fatal error C1192: #using failed on 'f:\bug\Lib\obj\Debug\Lib.dll'Build Time 0:00Build log was saved at "file://f:\bug\Imp\Release\BuildLog.htm"Imp - 1 error(s), 0 warning(s)---------------------- Done ----------------------Build: 1 succeeded, 1 failed, 0 skippedThe messages from a failed command line build...F:\bug>devenv /build Release /project Imp bug.slnMicrosoft (R) Development Environment Version 7.10.3077.Copyright (C) Microsoft Corp 1984-2001. All rights reserved.------ Build started: Project: Lib, Configuration: Release .NET ------Preparing resources...Updating references...Performing main compilation...Build complete -- 0 errors, 0 warningsBuilding satellite assemblies...------ Build