I am following this guide
https://msdn.microsoft.com/en-us/library/windows/hardware/hh439665(v=vs.85).aspx
I am using visual studio 2015 with wdk 10. However, when i am trying to build the solution (step 14), I get the following error:
command-line error: exception handling option can be used only when compiling C++ in line 1
Any ideas ?
Thank you
It's simple. There is a bug in VS 2015. You need to wait for VS 2015 Update 1, there is no workaround.
https://connect.microsoft.com/VisualStudio/feedback/details/1623363/error-command-line-error-exception-handling-option-can-be-used-only-when-compiling-c
C++ is usually not used in kernel mode drivers because it is not supported.
I see this same issue with VS 2015. Just create a blank C file in your project and you will see the intellisense (~) at the first column of the first line. This means intellisense is essentially broken for all C source files now.
Related
I've also raised this here https://github.com/nkdAgility/azure-devops-migration-tools/issues/1241 as a followup to https://github.com/nkdAgility/azure-devops-migration-tools/issues/1189 which i solved but essentially I'm still on the same processor the first of seven in my plan.
I am trying to do a single project migration from TFS 2019 to ADO Version
Dev19.M204.1 (AzureDevOps_M204_20220601.5)
I have 7 processors I'd like to get working however I just have the 1 set to enable right now as a starter and plan to work my way through them.
I'm getting an error telling me the TfsAreaAndIterationProcessor TfsEndpoint needs to be of $type = TfsWorkItemEndpoint and displays a System exception. However as far as I can see that's exactly what I have in my config file so not sure what I'm missing here.
2022-08-22 16:41:13.707 +12:00 [FTL] Error while running TfsAreaAndIterationProcessor
System.Exception: The Source endpoint configured must be of type TfsWorkItemEndpoint
at MigrationTools.Processors.TfsAreaAndIterationProcessor.EnsureConfigured() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\Processors\TfsAreaAndIterationProcessor.cs:line 67
at MigrationTools.Processors.TfsAreaAndIterationProcessor.InternalExecute() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\Processors\TfsAreaAndIterationProcessor.cs:line 38
at MigrationTools.Processors.Processor.Execute() in D:\a\1\s\src\MigrationTools\Processors\Processor.cs:line 106
One of the main difficulties I'm having with this entire process is that the available documentation seems a little sparse in terms of specific examples especially up to date examples that will work in 2022 with the 12.0.12.0 version of the tool which I'm trying to use so please bear with me as I have no experience in doing a migration to date.
Any assistance appreciated.
Additional info to explain my process: I'm assuming that this processor has to work correctly before the next processor I have lined up will then work e.g. the TfsTeamSettingsProcessorOptions and so on for sharedqueries, workitems, test configutations and so on?
After quite a bit of searching and trying different things, I am stumped on how to get mym to work (as found here: http://sourceforge.net/projects/mym/). I was wondering if anyone has a very simple list of actions needed to get this to work. I think my main trouble is installing zlib. I don't understand how to actually install it or work with it. I have tried to use Microsoft Visual C++ Express 2010 but then only the debug versions are compiled. That means when I try to use the mex function in matlab it gives me the error:
Error: Could not detect a compiler on local system
which can compile the specified input file(s)
I just don't understand the process and everywhere I look it says something different. I have tried multiple versions of each all of the programs involved and nothing seems to work. Any help would be greatly appreciated.
Do:
mex -setup
from the command line to define your compiler on your system. Once you do that then Matlab will correctly locate the compiler and build the mex libraries it needs.
See:
http://www.mathworks.com/help/matlab/matlab_external/building-mex-files.html
I'm a beginner to JavaScript and I am learning the fundamentals at the moment.
I have used visual studio before for code such as C# and VB and have a decent understand of how it highlights errors etc and shows build errors and what not.
Here is a small bit of code I've written in VS2012 in a HTML 5 file and the issue I have is it has 2 very obvious syntax errors however it does not highlight them and the page is allowed to run in both Firefox/Internet Explorer. The page obviously doesn't work and had I not known this syntax is wrong I wouldn't have been able to diagnose it.
http://pastebin.com/LX4L7YiD
Now I have looked at this topic : VS 2012 Syntax highlighting
I can't seem to make out from the above topic what exagtly I need to do to try that fix or even if that fix is relevant to my issue. The poster talks about what he's done but I don't understand how or what he's done.
Your code doesn't actually have any syntax errors.
Semicolons are optional, and variables do not need to be declared.
If you want to get errors for those, install Web Essentials and turn on JSHint.
(and add "use strict"; to your code)
I am running this on my machine
"%ProgramFiles(x86)%\Microsoft Visual Studio 10.0\Common7\IDE\mstest.exe" /testcontainer:"C:\Working\Einstein\Solutions\EinsteinAcceptanceTests\bin\Debug\EinsteinAcceptanceTests.dll" /resultsfile:TestResult.trx"
And I get
index was outside the bounds of the array
message back.
Any clue on how to debug this?
You may check for version incompatibility. E.g. you get this error when trying to run VS2008 Tests with VS2010 mstest.exe.
It happened to me in VS 2012, the problem being that I had 2 unit test projects referencing to different versions of the assembly 'Microsoft.VisualStudio.QualityTools.UnitTestFramework'
I saw the problem when compiling the solution, in the output window from the test section:
------ Discover test started ------
index was outside the bounds of the array
I just started working with the Visual Studio 2010 Premium database project. I must say it does indeed rock. One thing I can't figure out is how to avoid the SQL04151 warning
Procedure: [dbo].[MyProc] has an
unresolved reference to object
[MyDatabase].[dbo].[MyItem].
Did I miss a simple step somewhere? All I can find online involves tempdb.
I need to substitute [MyDatabase].[dbo].[MyTable] with [$(DatabaseName)].[dbo].[MyTable]. This cleared up the warnings.
Thanks for your help.
In your [dbo].[MyProc] procedure you reference [MyDatabase].[dbo].[MyItem] which is probably not part of your DB project. Even though the object exists in the DB, it is not known to Visual Studio during compilation and thus yields an error.
Normally you should have the entire DB-schema in the DB-project. Otherwise I think there is something called "partial DB projects" that you can look into.
MS has acknowledged this as a bug they are working on:
https://connect.microsoft.com/VisualStudio/feedback/details/543657/4151-unresolved-reference-warning-for-tempdb
Check you have set Build Action to Build on Properties pane for the specified object..