For an external library I need to build and run it on x64 configuration.
It seems to do this on every project despite the setting in the publish window. It does seem to honor the Release/Debug setting, but not the Platform setting.
How to proceed?
It seems to do this on every project despite the setting in the
publish window.
The Any CPU won't change because It's a default platform(Like a name), and the any settings actually are changed. That's why your Debug Output always shows "Debug:Any CPU".
This setting could be change,
Build->Configuration Manager->Project Platform->New
After these you go back to your Project Properties ->Build and click Platform x64 will be there. You could also switch them here.
Hope this could help you, if you still have other questions, please let me know.
Related
While working with some projects checked out from Git, we get errors with modifying the project settings in MyEclipse. I am trying to modify the deployment values in my workspace and it is not letting me (screenshot below).
There isn't a lot of information to go on, here (e.g. what is the version of MyEclipse, what type of project is this, what properties page are you switching from, the OS and version, whether this has worked before, the error log - but please don't paste that in here - and so on).
However, here are some actions that might help resolve it:
Firstly, try a fresh empty workspace then import the project from the old workspace, or better still import again from Git. This would help clean up possibly corrupted settings in the workspace.
Another thing to try is to launch MyEclipse with the -clean option (just add that option to the top of your myeclipse.ini file, found in the installation folder).
#Howlger is right, though, this is a commercial product and we may be better able to help if you raised the issue in the MyEclipse support forums.
I have a windows application and using cheetah for config transformations i.e app.config.debug, app.config.test, etc.,
When the project is built in debug mode , it works fine but when teamcity change the mode to test configuration and try to rebuild getting the following error:
/platform:anycpu32bitpreferred can only be used with /t:exe, /t:winexe and /t:appcontainerexe
Can anyone please help me how to fix this?
Thanks
Open the project file with the text editor. Find the line <Prefer32Bit>true</Prefer32Bit> and change the value "true" to "false". There might be more than one depending how many different configurations have been set up.
Removed true from one of the project. It worked.
But not sure how this entry was added to that particular project.
For me the issue was that the project listed in the error had the wrong configuration setup. So while the Configuration Platform for the current build was set to x86, the target platform in the properties for the x86 configuration was set to AnyCPU.
So for OP sounds like the configuration is correct for the Debug build, but your target platform may not match the platform specified in your test configuration profile.
If you experience this issue please check that the target platform in the build properties for your project match the configuration platform.
There are a million links like this one http://blogs.msdn.com/b/cie/archive/2014/01/24/windows-azure-remote-debugging.aspx, which more or less would seem to take care of the remote debugging setup. I have done this many times in VS 2013 Update 2, deployed, then attached to debugger and it simply does not work. Well, the debugger seems to attach, but I continually get the message when I hover over a break point informing me that 'The breakpoint will currently not be hit. No symbols have been loaded for this document' A while back I recall seeing a channel 9 presentation and they seemed to configre the symbol store. I tried configuring this and it still gives me the same message when hovering over the breakpoint.
VS 2013 Update 2 Remote Debugging - I can only get it to work with a 'Debug' build. I have set the Debugging Option "Enable Just My Code" and loaded all symbols -- this seems to work fine. I can now set breakpoints and do not receive the message you (and I) noted earlier.
This is probably not the ideal situation as it would be nice to be able to attach the debugger to a production release but it seems to be a semi-reasonable workaround for now.
EDIT:
Important points:
You must enable Remote Debugging in the Azure Portal for your Cloud Service or Web Site -- Configure Tab (it only remains enabled for 48 Hours)
The debug attribute of the compilation element in your Web.config file must be set to "true". This means, you either have to do a 'Debug' build or manually edit the Web.config file. Here is a link to official Microsoft documentation with a full explanation and a great example of how to do that without redeploying your application:
http://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/#remotedebug
If you still have problems you may have to disable the Debugging Option Enable Just My Code in Visual Studio
I had the same problem - also with VS 2013 Update 2.
The crucial bit I missed was selecting the w3wp.exe process in the pop-up that shows the running processes before hitting the Attach button.
So I imagine this is a pretty simple problem, but I can't find anything about it.
I've set up CruiseControl.Net to check my svn repository for any changes every 30 seconds, and if there are any changes, build them using NAnt.
Everything works great - but only if I have the CruiseControl.Net console running at all time on the server. If I close the console, it won't check for changes and build them. I've checked the wiki for a way to set up continuous monitoring, but I can't find anything
Does the console always need to be running in order to detect changes, or is there another way to do this?
There are two ways to run CCNET: As console application or as windows service. You're looking for windows service mode.
Here is a tutorial on "Installing CCService". Be aware that this documentation is outdated. But it should give you an impression.
Installing CCNET as a windows service is an option during CCNET installation so this is the easiest way to get it up and running.
I just deployed a website into IIS 7 (about which I am woefully ignorant), and upon trying to build the site, I receive this error. I did a little googleing and I saw an article that said I should put system.web.extensions.dll into the /bin. But, I also saw an article saying not to do that. I tried it anyway, but I just received a different error ('Resource cannot be found').
I am totally clueless as to what else to try
Can you use the "Publish" command in Visual Studio to publish directly to the site? If not, then use that command to publish to a similar site on your machine, then copy it to the customer site.
You should also look into the IIS Web Deployment Tool. It can copy an entire site, including IIS settings and any databases. It will be built into VS2010.
Go to control panel, then programs, turn windows features on or off, scroll down to Microsoft.net framework 3.5.1 expand, make sure both sub options are selected, this might help your issue.