Iv'e downloaded a C# interval tree collection class class from here http://intervaltree.codeplex.com/SourceControl/list/changesets -> Right hand side -> Download.
However I can't open the whole project on my Microsoft Visual C# 2010 Express (that also runs C# XNA) because
Solution folders are not supported in this version of the application
Also I just want the class to use separately in my own seprate project.
I tried to copy the three important seeming files Interval.cs, IntervalNode.cs and IntervalTree.cs into my project but this generated the compile error
There are no importers which handle this file type
I've also tried to copy and paste the contents of the three files into my project, encapsulating them into there own namespace as well as there was a lot of code. I had to rearange some of the usings a little but have run into the problem that possibly it wants PowerCollections .dll and .pcb files as using Wintellect.PowerCollections; causes
The type or namespace name 'Wintellect' could not be found (are you missing a using directive or an assembly reference?)
I'm not sure how to continue or if I'm doing the right thing at all in how to get this class to work.
Add the library to your solution
Copy the IntervalTreeLib directory into your solution directory. Then, right-click your solution, and add existing project. Point it at IntervalTreeLib.csproj in IntervalTreeLib, and click Open. That should add the IntervalTreeLib project to your solution.
Add a reference to the library in your project
Then, in your project, add a reference to the IntervalTreeLib proejct:
- Right click the References folder, and Add Reference. Click the Projects tab, and select IntervalTreeLib.
Use the classes in your code
To use classes from the library in your source then, you need to either add:
using IntervalTreeLib;
void Foo() {
IntervalTree<int, int> tree = new ...
}
Or, refer to them by their full name:
IntervalTreeLib.IntervalTree<int, int> tree = new ...
Open the IntervalTreeLib.csproj file if you want to be able to open the project in it's entirety (or in your current solution add an existing project (you can right-click on the solution) and select the IntervalTreeLib.csproj). If you are trying to grab just the code file in your project, ensure you also grab the PowerCollections.dll file (I see it is in the same folder as the code files) or your code will not compile (as you have discovered). You'll need to add a reference to it and include the needed using statement at the top of the code files making use of this library (or use fully qualified name with the namespace).
using IntervalTreeLib;
or
var myObj = new IntervalTreeLib.[WhateverClass](...);
Also, make sure you read the license.txt file. You may need to include it if you are using the code. Give credit where it is due.
UPDATE:
If the test project is causing you problems, just open the library project. Ideally you could just open that and compile it, adding the output DLL files that are generated directly into your solution. This is ideal unless you are planning on changing the library source code itself.
Add the library to the references of the project you want to use it.
Since discussing that you are able to build Intervallib.dll, we will discuss about how you should the dll in your project.
Now in your proj, right click on the references part and add the dll intervallib.dll to your references. In your game.cs file, have the reference to the namespace as -- using IntervalTreeLib;
then you should actually copy the dll powercollections.dll to the bin directory of proj directory also.
you should copy this dll because there is an indirect link to the dll as it is used in IntervalTreeLib.dll
following these steps, I was able to execute this project.
When moving files around in a project I ran into some pretty frustrating namespace collision issues. After the fact I learned a better way to move the files but I'm hoping to find a solution. Here is what I experienced:
After moving files via cut/paste I had a namespace collision (I have many pages with the same name in different folders e.g. Foo/Add.aspx and Bar/Add.aspx). When I moved a page, associated code behind and designer to a new folder I had a namespace collision. When I updated the namespace VS showed the little red marker indicating it wanted to "help" me by renaming. I had VS go ahead and "help" only to find after several attempts that it was also re-naming the file in the folder I had moved from e.g. When I renamed Foo/Add.aspx VS was also changing the namespace for Bar/Add.aspx
Does anyone know why this is? Or how to avoid it? I fixed it by manually changing all my namespaces and not allowing VS to "help" me out.
There are a few options:
if you have Resharper then use the Move function
don't copy/paste with a project, instead you should drag/drop - that way the proj file is updated and files maintain their relationship (i.e. when you have generated code behind, etc). Then the moment you've dropped, go and change the namespace in the dropped file.
create a new file in the target folder, then just copy the contents (everything inside the namespace declaration) of the old file across. The new file will already automatically have an appropriate namespace defined.
None of this tidies up any code that references the old code that has been replicated/moved. You'll have to fix those references yourself, unless you use Resharper (which does that for you as part of the move).
If you're talking about class namespaces, the problem is that VS has no way to know which "Add" namespace you want to rename. It just renames all the ones (in its current scope) that match that current name to the new name. If you want to avoid that happening, they will need to at least be in different VS Projects. VS does not care about file names or paths, except to the minimum degree needed to find them for compiling.
what I do is, I always create my class in the destination project and copy the content of the source class to the destination class. in this way you will be safe.
I doubt if there is a any magical way to avoid that problem.
I have a solution that includes various C# projects, and I just now noticed that I can't change the default namespace on any of them.
When I go to Properties --> Application on any of the project and change the "Default Namespace" field, a fatal error dialog pops up that says:
exception of type 'system.runtime.interopservices.externalexception' was thrown
At this point Visual Studio becomes unusable, as I can't close it or leave the screen, every click or button combination I press makes the same dialog pop up. The only thing I can do is terminate VS with the task manager.
I got around it by just renaming the <RootNamespace> node in the .csproj file
Maybe you should try to do this in another way:
Ctrl-H - Find: PreviousNameSpaceName Replace: NewNamespaceName
You can also right click the namespace in code and Refactor->Rename.
What is more: you can change the names of your projects, solutions, directories - etc. Namespaces, when adding new files, are generated using these names in fact.
I had to investigate the issue in our company and I found another workaround in our case. So I think it make sense to add it here.
Possible Solution
Check if you have more than one suo-File for the project/solution and delete the one which doesn't has the ".v12.suo" naming (better delete both)
Story behind:
We still have two Visual Studio installed (2010 and 2013) and some of our developer worked recently on 2010. So they had on the file system a regular ".suo"-File. Afterwards (some weeks later) they started to use 2013 (which created a ".v12.suo"-File).
We renamed both suo files, started VS2013 (which created the v12.suo) and were able to rename the namespace without a crash. In addition we had this issue not on all solutions. I didn't see yet a pattern, but in our case it happened mostly on solution with at least two projects and referenced project-libraries.
I am a long year Java programmer, but currently I code in C#. I am accustomed, that when I change filename, also the class name changes and vice versa. This doesn't work in my Visual Studio. I must rename the class name and file name separately, and it's sometimes annoying for me, because I always forget on it, so it results to that I have different class and file names.
Is there option in Visual Studio to put the renaming in one step?
Renaming a file works fine - it'll offer to change the code to match:
If you rename the class, then - indeed, this doesn't happen by default. There is no actual need for the two to match, note. But ultimately, rename is only an f2 away.
As of Visual Studio 2015 Preview 5, the "Quick Actions and Refactorings" context menu contains a "Rename file to [class].cs" command.
It seems to not work when the copied file is in the same folder and the class name is the same (which it will be if you just copied the file). I think the reasoning may be that rename doesn't descriminate between a class in a newly copied file and the original (See comment below by #xMichal).
The quick solution is to copy the file (I use ctrl+drag) into a nearby folder, rename, then move it back.
Another option (which may be Resharper specific), is to rename the class (and constructors) in the copied file, then use the tooltip to electively rename the file to match.
ReSharper has the MoveTypesIntoMatchingFiles menu option on the Refactor context menu, and it seems to do the trick. Just that if you have more than one class in the same file, they will be moved also into separate files, but that should be a good thing in most cases anyway.
Install the awesome visual studio plugin called Reshaper.
It does that and loads of other nice stuff.
Free for 30 days then its costs but is definitely worth it.
If you 'refactor' something, the name will be changed everywhere where that text or name has been used so you don't have to follow up changing the name every time its been used. However, you cannot do that with objects beyond the project eg: file name.
Specifically the error occurs in the Resources.Designer.cs:
Error 2 The namespace 'ModulusFE' already contains a definition for 'StockChartX' Resources.Designer.cs 11 21 ModulusFE.StockChartX
I've googled this and am still quite confused. Does anyone know anything I might try?
I have tried rebuilding and cleaning, as well as renaming the Resources.Designer.cs file in hopes that it would rebuild, but no luck.
The top of the code says this:
// <auto-generated>
// This code was generated by a tool.
// Runtime Version:4.0.30319.225
//
// Changes to this file may cause incorrect behavior and will be lost if
// the code is regenerated.
// </auto-generated>
Any ideas whatsoever would be appreciated.
Looks like a bug in VS code's OmniSharp.
Solution for me was to execute command "Restart OmniSharp".
Just do:
- ctr shift P
- type "Restart OmniSharp" .. hit enter
This fixed it for me.
I had this happen to me about a year ago and I don't remember exactly what the root cause was, but there are two things you might try:
If it's an auto-generated file (as 'Resources.Designer.cs' tend to be), try deleting it and letting VS re-generate it.
Either separately or in conjunction with #1, select Show All Files in the Solution Explorer or open the solution folder in Windows Explorer - it could be that a version of the file somehow got excluded from the project and is therefor 'invisible' to VS but still makes it angry...
I've had this problem, too, and it was because I created a new namespace, but the parent namespace contained a class with the same name.
This is an old question but I didn't find the fix I used, so I've added it here.
In my case it was a namespace with the same name as a class in the parent namespace.
To find this, I used the object browser and searched for the name of the item that was already defined.
If it won't let you do this while you still have the error then temporarily change the name of the item it is complaining about and then find the offending item.
Unfortunately, none of the other answers helped.
My problem specifically occurred in a WPF project.
The problem arose when I created a folder under the MainWindow folder, which effectively created a namespace something like ProjectName.MainWindow.Folder.
Now, I believe because of some static designer code, Visual studio gets confused between the class MainWindow and the namespace Project.MainWindow.Folder .
As a solution, I moved the Folder out of MainWindow. Looking at the Class View or the solution/project helps to recognize what namespaces and classes within them exist.
This just happened to me. What happened was that I duplicated a project that was originally under source control. Although I properly renamed everything, the file permissions on all the files were still set to read-only. When I started modifying some form controls, Visual Studio automatically created a Resource1 file because the original Resource file was read-only.
What I did to fix this was as follows:
allow write permissions on the project files.
deleted the original Resource file
Ctrl-A for all form elements, then Ctrl-X to cut them.
Save the form.
Ctrl-V to paste them all back.
Save the form.
I had to do this because the auto-generated code wasn't updating on it's own, so I "forced" it to update by making a change to the form. Not doing this left a bunch of code from form elements that no longer existed prior to changing the file permissions.
I had an xaml file with the following definition
<Window x:Class="mm2.Views"
.etc..
/>
mm2.Views was the name of a namespace in my app.
To fix it, I correctly renamed the xaml object:
<Window x:Class="mm2.Views.RecordedTracks"
.etc..
/>
I had a similar problem and resolved it by removing any copies/backups of the .cs file from the directory.
I had this same problem and it was due to naming a function in the code behind the same as my tool. Simple mistake but something to keep in mind as well.
I had a similar issue however found a different solution than what I have read. I came to my fix after reading P Walker's answer.
My issue happened when I named my resource file for Japanese language incorrectly. Long story short I was trying to create a Resource for Japanese but I accidentally named it localized.jp.resx. I then realized that the iso language code is ja not jp for Japanese. Once I changed the file name to localized.ja.resx and deleted everything that was in the designer file it fixed my problem.
This is what fixed my problem hopefully it helps someone else.
I came across a similar problem. After generating my database from an edmx file, I clicked 'save all' and 'build' and all the Types/Model classes that I created showed up in the error box. I researched why this happened and like your replies suggest, I thought it was something that was auto-generated.
However, solutions like deleting the auto-generated classes and re-generating them didn't work for me.
I eventually ran out of patience and decided I'd fix it another way. Since my script was saved, I just deleted the edmx file (and its reference in the web.config) and went back and created another one using "model from database" and didn't touch it after that.
Needless to say, I was pretty mad that it turned out like that.
Me too got this error,
When I change my WPF project's Target Framework to Framework Version 4.0 Client Profile -> Framework 4.0. It's solved by itself.
The way I solved it was to remove all of the enums from the model browser, and then re-add them again. Somehow miraculously the tool regenerated everything perfectly and the error message went away (I'm using VS2012, FYI).
What helped me many times, was just turning it off and on again..
Ctrp + shift + P -> Reload window in VS Code
Close and open the project/window.
Cleaning all bin, obj contents (in power shell)
Get-ChildItem .\ -include bin,obj -Recurse | foreach ($_) { remove-item $_.fullname -Force -Recurse }
After this, it can be that I am missing something else, like some package reference or include, but usually it is, that underlying parser/compiler (omnisharp) just gets messed up and needs some restart to work properly again.
This may be a bit of an edge case, but we've run across this in our development environment from time to time. We had to setup a custom culture in Windows to support en-HK. Windows 8.1 now supports this culture natively as does Windows 2012 R2, but older machines need to have the culture created. Any machine that does not have this culture setup will get this error reported. The solution is to create the culture on the machine (We have a console app created for this purpose) and everything starts working again.
I had the same issue just now, and I found it to be one of the simplest of oversights. I was building classes, copying and pasting code from one class file to the others. When I changed the name of the class in, say Class2, for example, there was a dropdown next to the class name asking if I wanted to change all references to Class2, which, when I selected 'yes', it in turn changed Class1's name to Class2.
Like I said, this is a very simple oversight that had me scratching my head for a short while, but double check your other files, especially the source file you copied from to ensure that VS didn't change the name on you, behind the scenes.
If you are using different aspx.cs files that define classes of the same name you can use
<compilation targetFramework="4.5" />
under <system.web> in your web.config file.
Although I would still strongly advise that you would change the class name.
This is not the best solve, but if you really don't care it is an easy solution.
I simply renamed my class. So I had class Card and I changed it to MyCard.
I think this issue is because you have added for a single table, 2 DAL classes.
If this table is included in a relation, then remove the table_name.dbml for it, and keep that for the related tables.
You must use one of them.
I had a similar problem (Universal project, Visual Studio 2015), I solved it with the following changes:
In App.xml.cs was (it was ok):
namespace Test.Main {
Wrong, old version of App.xml:
x:Class="Test.Main"
Good, new version of App.xml:
x:Class="Test.Main.App"
I had something similar to this happen in my WPF application. It arose when I was trying to do some cleanup by declaring a namespace that was more descriptive. The problem arose because I had named the namespace in the code-behind (or cs) the same as the Window class. The namespace in the code-behind should have the last section stripped (after the rightmost dot) and used to declare the class and instantiate it. Notice Win below:
xaml
<Window x:Class="FrameApp.UI.Invoice.Win" ...>
code-behind
namespace FrameApp.UI.Invoice
{
public partial class Win : Window
{
public Win()
}
}
An obvious oversight but it set me back at least an hour with all the errors that appeared.
I had this issue, but mine was slightly different to the issues mentioned here. I was cleaning up my project and moving around some classes into new folders. I had a 'AddFilter' class that I moved into an 'AddFilter' folder - so I had actually wound up with a class that was sharing the name of a namespace. This was a bit tricky to spot at first because I couldn't find any other classes that it was conflicting with; it was conflicting with the namespace instead.
If you copy&paste your pages don't forget to rename class names. Otherwise you get this error also with "Type already defines a member called 'OnGet' with the same parameter types"
look this happend to me when I created new file inside a folder with the same name of class in the project { folder name : Folder } and there is class name { Folder } so the namespace was the namespace.Folder so that the compiler assume that the cass defined in two places
in new file :
namespace APP.Folder
{
partial class NewFile
{
// ....
}
}
in the other file (the file that hase the problem):
namespace APP
{
partial class Folder
{
// ....
}
}
-- so you can edit the folder name or remove the .Folder from the namespace at the new file
I know this is an older post, but I thought it might help someone else if I shared my experience with this error. For me, I was working in Visual Studio 2019 and using Xamarin Forms. I received this error message when I created a new folder and named it the same as a Content Page I had made previously. Apparently we're not supposed to do that...
Anyways, I had to rename the folder then go through to each individual Content Page within the folder are change their namespace (in their .cs file) as well as the x:Class within their ContentPage tag (in their .xaml file) to reflect the folder's new name.
That's what worked for me. I hope it is helpful to someone else in the future should the error rise again.
I've had this problem recently, all i did is rename the file and class then build. then return again the original filename. It worked.
This happened to me, I noticed that there was actually another class with that same name under the same namespace "OtpService.Models.Request", so all I did was to just change the namespace of the 2nd class to "OtpService.Models.Request.ExtraObj". I did this because I did not want to change the name of the conflicting class to anything else.
I came across this partial class problem in a winform of a solution after converting from .net 4.5.1 to 4.7.2.
Initially the problem the compiler was not complaining about partial class but the use of properties.default...without qualification. After adding Global::solnNameSpace. qualifiers, then I got the partial class problem.
after viewing answers in this thread, I look at the resource designer file, I found it was generated with explicit solnNameSpace while the classes in the solution did not. Also the solnNameSpace is the same as the name of the problematic class name.
To fix the problem with the least effort and time I backed out Global... qualifier and removed the explicit namespace ... and end statements from the resource designer file. I know I may get in trouble later on if there were changes that cause auto generation of the resource designer file but I was was under tight deadline. I made documentation on the temp change instead of a better long term solution since the solution is under no change allowed for nature of the solution and multi project use.
I had this problem. It was due to me renaming a folder in the App_Code directory and releasing to my iis site folder. The original named folder was still present in my target directory - hence duplicate - (I don't do a full delete of target before copying) Anyway removing the old folder fixed this.
when you have tried everything else and still get the same trouble, there is a way out; however it will be tedious and need careful preparation.
Start another new project using existing files, or edit the project .csproj file if you are proficient in editing csproj (need backup). I will list steps for new project.
preparation:
note all references and their sources
note all included files from another project
rename the orginal projectname.csproj file
close solution/project
start new project using existing files(you will get errors from references)
add back the noted references
include/add existing file from other project(s)