Even without selecting a WSDL, if I click on the Advanced button on the Add Service Reference dialog in Visual Studio 2008 on a specific project, I get the following error:
An error occured while parsing EntityName. Line 2, position 47.
Anyone run into this before?
this must be problem of your webservice class, there might be some errors in that.
The WSDL published from the server may be broken, you may try the command line tool (svcutil) to test it, though the VS uses the same tool indeed.
Related
The Autodesk ObjectARX project wizards fail to create projects in visual studio professional. I only see in the status bar at the bottom that it has failed. How can I tell what's wrong?
I've checked the visual studio logs (using devenv.exe /log) with nothing reported. And I don't see any other logs. What else can I do?
I should add that there should be a ui, but nothing appears. It fails right away.
Uninstall the wizard.
Right click on wizard setup file
Troubleshoot compatibility and follow steps to install
Try, it works
You should put the ObjectARX folders (inc, lib or so) to "C:\ObjectARX".
Another place is unacceptable.
I had the same problem because on wizard 2018 installation leave field "Registered Developer Symbol" empty. Then on using wizard you can change this symbol to any other.
Other name for ObjectARX directory allow successfully install wizard 2018 but then will be problem in project settings where this path hardcoded as c:\ObjectARX. So better use c:\ObjectARX.
I'm trying to compile a project I have in Visual Studio 2010. It has built fine on 2 other computers with Visual Studio, but on this computer, it will not compile, and returns:
"The property could not be read/written because the language service returned an unknown error"
Obviously, I have tried googling, and nothing of any use came up, so some help would be great.
Additional Information:
Project is an XNA 4.0 Project
Trying to deploy the solution to a Windows phone. The phone is plugged in, unlocked, etc. and other projects will deploy successfully to it.
I've run into the exact same error message when I tried editing the AssemblyInfo.cs using VS 2010's Assembly Information dialog from within the project properties (open Properties -> Application from below the given project).
As this thread suggests, I deleted the AssemblyInfo.cs file and filled in the values I wanted in the dialog box which created a new and working AssemblyInfo.cs. Maybe this would help/would have helped in your scenario as well.
Note, that you'll get a fresh and valid GUID if you simply click save after opening the dialog.
I encountered this today in VS 2017. It went away as soon as I performed a build which fetched all my references.
This has been driving me crazy for months. I have a multiple projects that compile without errors. If I start copying and pasting controls (or even just plain 'p' tags) the designer will fail 1/2 the time with the error "the method or operation is not implemented". The complexity of the page doesn't matter. The 'solution' is to delete the designer file, exit visual studio, open visual studio and convert the offending aspx file to a 'web application' to regenerate the designer file.
This is a really annoying. I can't find any fixes on Google. Is there a way to disable the automatic designer file? Make it so it only generates on a 'build' command and not fail everytime I'm laying out a aspx page?
Thanks
To find the fix for the issue you would need to find the cause of the issue. It might be possible to get more information on what is causing the issue if you attach a debugger to Visual Studio. This could be done by following these steps:
Open two instances of visual studio (run as administrator)
In one, open your project and get to a point right before the issue occurs
Attach the other instance of Visual Studio to the one with your project (Tools -> Attach to Process)
Perform the steps to reproduce the issue.
Note that to actually catch the exception you will need to change a few debugging options. First you would need to make sure that the Just My Code check box is unchecked in the General debugging options in Visual Studio. The second is on the exceptions dialog you will need to catch thrown exceptions. The exception dialog is under the Debug menu in Visual Studio.
When I'm trying to change the default Image of a Control on Windows Forms in Form Designer (no matter where on which control) I get this error:
Error message: An item with the same
key has already been added
I tried to delete and recreate the Resources.resx file.. I assured that only 1 resx file with these keys exist.. (in fact that's my only resource file) but it still does not work.
I have som strings in it and some images. That's all.
Any idea?
I had this problem too. The solution is to never create a .resx file with the name "Resources.resx" because it conflicts with the "Resources.resx" files that can be automatically created in the project's properties dialog.
Just right-click and rename the "Resources.resx" and you should be able to change images perfectly.
If you really want to figure out what is going wrong, you can try and attach a debugger to VS and break while devenv.exe is showing the message box. From the call stack it should be obvious what VS is doing. Here are more details about debugging Visual Studio: http://blogs.msdn.com/kirillosenkov/archive/2008/12/07/how-to-debug-crashes-and-hangs.aspx
If you like, you can post the call stack of the Visual Studio main thread here and I can try to investigate what is going on.
Was getting this error while adding a project to a solution. None of the above metioned scenarios applied but restarting visual studio fixed this. Silly, yes.
Visual studio version - 2015 enterprise.
I had the same issue. But in my case it was because I had twice the same file listed in my resources folder.
Probably a problem after a merge.
I was looking around the net for a NUnit custom MSBuild task that would run on every build and also nicely play with Visual Studio UI (2008 is my version). I found MSBuild.Community.Tasks project that was great, but failed in Visual Studio integration part.
What I actually wanted to have is get failed tests displayed as warnings/errors in VS's error list window (and also FAILED project build when tests are not successful). So I wrote my own custom MSBuild task that does the job exactly how I wanted it to be.
BUT.
The only problem that I have is that normal VS UI error list behaviour is that when you click on an error it jumps to appropriate source file and highlights the problematic code. I was able to relate file and line number with failed test however I wasn't able in any way to persuade Visual Studio to HIGHLIGHT problematic code for me (when I double click the error). All I get is cursor in the right spot.
I tried all kinds of combinations of line, endLine, column, endColumn method parameters (Log.LogError()), but to no avail. And based on error output by compiler errors it looks like it also provides just line and column (no end values).
Anybody ran against this oddity and solved it?
Update 13 May 2009
You can get this project for free (without method selection) at
http://code.google.com/p/nunitmsbuildvsintegrated/
For this feature, you must create Visual Studio Integrated Package that display custom panel in Visual Studio. This custom panel will be called when your project is built.
Visual Studio Extensibility Developer Center
I have no solution to your exact problem, but have some thoughts.
Are you sure you want to run a full suite of unit tests at the end of each and every build? I personally find it to be a productivity killer. Rather, while working with code I tend to run a small subset tests which cover only the code in question, and this is where tools like ReSharper or TestDriven.NET come into play.
(source: jetbrains.com)