As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Do you know of software like MS Visual Studio for Mac ?
There is a free suite of tools called Xcode which you can download from Apple's developer site. It gives you an IDE, all the different compilers, a bunch of tools, etc.
For mono development: http://monodevelop.com/. Assuming thats what you mean by visual studio and using .NET.
For native mac apps XCode: http://developer.apple.com/technologies/tools/xcode.html.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
NOTE: This question discusses TFS-2012 vs SVN. Similar (but not duplicate) questions compared earlier TFS versions.
From what I've found (on other questions and sites), Microsoft has fixed most of the earlier gripes (performance, features, etc) of the earlier versions of TFS (as compared to SVN).
What are the primary pros and cons between Team Foundation Server 2012 and a Subversion solution (TortoiseSVN, VisualSVN, AnkhSVN)? What TFS issues remain? What does svn provide that just isn't available in TFS?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Our team is thinking of upgrading to Visual Studio 2012, are there any common bugs that may cause hassle? Typically when a system is released, there are a few major bugs that were missed completely by the development team (eg. The entire Vista operating system)
I don't know of any "known" issues for VS 2012. There's usually a note or two in the readme; but, I cannot find one. You can view all the bugs (and other feedback) on Connect http://connect.microsoft.com/VisualStudio/SearchResults.aspx?FeedbackType=0&Status=1&Scope=0&SortOrder=5&TabView=0
Also, there's a UserVoice site for Visual Studio, so you can see what other people are suggesting to see if there is anything there that might be a show-stopper: http://visualstudio.uservoice.com/forums/121579-visual-studio
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am trying to debug some assembler code on windows. For 32 bit code I was using Ollydbg, but it is unable to open 64-bit exe files.
I also tried using the visual studio debugger but I think the stack is somehow getting corrupted and I can't figure out how to place a breakpoint at the program entry, so this doesn't work
So are there any free programs that work?
If it matters I am using nasm and then gcc to compile the exe's
why not give windbg a try, its made by MS and free, here's the 64bit version.
Visual studion has an excellent debugger for both 32 bit and 64 bit windows.
If you are using nasm or yasm assembler then use the option -gcv8 on the assembler. This produces debug info that works with visual studio. You have to make a project in VS that includes both C/C++ and asm files. The asm files need a custom build rule looking something like:
CommandLine="yasm -fwin64 -gcv8 -o$(InputName).obj [inputs]"
Outputs="$(InputName).obj"
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Could you please recommend me a good application level debugger for Windows 7 x64? It is not needed to debug 64-bit applications; it must only run reliably within a 64-bit environment.
I am searching for something like OllyDbg (http://www.ollydbg.de/). However, the problem with OllyDbg is that it is not yet ported for Windows 7 x64.
This has been tried:
SoftICE (does not work for Win7 x64)
Syser (it was giving me error messages after installation)
WinDBG (this one looked too complex and slow to learn. I did not like floating windows all around)
IDA pro (this one did not allow me to debug application. It only listed the structure graph)
OllyDBG (after loading the application, it terminates it immediately. Probably a result of compatibility. I also checked emulating Windows XP SP3, but not help at all)
It is required to run the application in real time, and trace it in assembly language.
Both OllyDbg 1.10 and IDA pro works fine in Win7 x64.
For OllyDbg use Stealth64 plugin.
Visual Studio is decent as a program-binary debugger, it's excellent for programs with .pdb information and source code. Only the advanced version of IdaPro works on 64-bit OS's. From their website:
IDA Pro Standard supports the following families (64-bit analysis is possible only with the Advanced Edition)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Mole visualizer for WPF in Visual Studio is a great tool for debugging WPF apps. What I want to know is, is there a visualizer tool with Mole like functionality for general .Net debugging. I find the built in watch capabilities to be a little fidly.
Thanks
Since MOLE version 3.0, the tool has been able to work with all types of Visual Studio projects. See here for more information about the tool and how to get the latest version.
Mole 2010 works for all .net objects. I just used it for a winforms app and a WCF service and it works great.
They've got a free demo if you want to check it out http://www.molosoft.com
Cheers!