I'm working on a windows form application. I start a new project. I delete the Form1 stuff from the new project. I go and add from existing in the solution explorer and choose Form1.cs, Form1.Designer.cs, and Form1.resx from another project. When I look at the designer Form1 just looks blank, like a new one would with none of the controls appearing. The program still compiles fine with all it's controls intact. Did I miss a step somewhere? I've closed and reopened the project etc. This happens every single time repeatedly so I believe I'm missing something but searching here or the rest of the web hasn't provided me a solution. Maybe it's just assumed to be known by everyone already?
I am just learning c# and Visual Studio so hopefully I didn't miss something stupid. I was following direction for how to do this from a book. Some projects are re-used to teach a new idea so they have you start a new project and add in existing items from the original to then work on the new idea.
In VS 2013 I chose "Add existing Item" and just selected the .cs files, don't add *.Designer.cs and *.resx files. Then waited for few minutes and restarted VS2013. Designer.cs and resx files appeared as associated with Forms but they were excluded. I right clicked them and chose "Include In Project". Then it worked fine.
Make sure that you are loading the Form1 that you think you are loading.
By default, Visual Studio 2013 (on Windows 7) will create a folder in Documents (C:\Users*Your user name*\Documents) called "Projects". Whenever you create a new project from within Visual Studio by going to File->New Project, Visual Studio will (by default) create a new folder in the Projects folder with the project name.
I think when you "delete" Form1, you're not actually deleting it, just removing it from the project. When you go to add Form1, you're just selecting it from the same project folder, when you actually wanted to load it from a different project folder.
Try this: In your current project (the one where you deleted Form1 and then added it), in the Solution Explorer, right click on the project, and select "Open Folder in File Explorer".
This will open the project folder on disk. Now, delete Form1.cs from within Visual Studio, and switch back to the project folder. If Form1.cs is still in that project folder, then you just removed it from the project. The actual files still exist on disk. When adding existing items, Visual Studio will typically default to the selected project folder.
I have a very strong suspicion that the Form1 that you are really looking for resides in a different project folder. Without knowing the book or tutorial you are following, I can't give you any hints as to where the Form1 you want is located.
I have a solution that includes two projects. My main project is a windows form and the other project includes two user controls that I created. I have a test form in the second project, and there I have no problem using the user controls from the toolbox. However, in my main project I cannot use the user controls.
I've found various 'solutions' online and tried them all with no success.
The problem is, the controls ARE in the toolbox, they are just grayed out.
I have:
Checked that both projects use the same .NET framework
Checked that autopopulate setting for the toolbox is true
Referenced the user control project
Have them both in the same solution
Rebuilt my project and solutions and restarted VS multiple times
Reset my toolbox
Clicked "choose items" and made sure the controls were checked
NOTE: If I create the user control programmatically, it compiles, shows up and works perfectly fine on run! I want it to show up in the designer though and not be gray in the toolbox.
Problem solved by going to the project (with the user controls) and changing the Output type to "Class Library" this builds a dll instead of an exe.
Rebuild the solution and controls were in the toolbox.
Make sure the control you want to add is a Public class.
I have created Visual Studio 2012 Package Project (from VS2012 SDK) with my own Custom Editor. It works fine. Editor is associated with solution files with *.myext extensions. Now, I would like to be able to create such a *.myext files with taking advantage of Add -> New Item.. option from context menu in Solution Explorer of VS2012. Thereafter, what is important, this additional functionality should create two files at one, similarly as it is performed by EF Entity Data Designer, WinForms designer, Resources designer, etc. First file with main editable content which is modified by Custom Editor (*.myext) and contains design schema, and the second file which is auto-generated and contains output (in my case XML) data (*.myext.xml.).
How can I register file type and implement that functionality?
This article shows how to add Items to the Add New Item Dialog Boxes. I'm sure it will be easy to find possibility to create two files instead of one.
Or you can add you own menu item to Add menu using VSPackage.
I've got a winforms that looks like the following:
It has an associated code file behind the controls.
It is located in solution X.
There are various other files in X.
I have created a new solution Y with a new blank winforms project in it.
When this is created a load of boilerplate code is created that relates to the blank form.
From X I'd like to import just the above design (with corresponding code) into this project to replace the existing blank form.
Is it easy to do this without confusing the existing project due to all the boilerplate code?
I've tried right-clicking the project in the Solution Expl and using Add > Existing Item but this just confuses the issue. Maybe this is a pointless exercise and I should just right-click the solution in the Solution Expl and using Add > Existing Project and then just delete the blank winforms project in the solution?
While you could just copy the relevant file(s) into the new project, it's better not to repeat yourself. So either "Add Exiting Item", but link the files from their original location...
...with the following result in solution explorer (note the "shortcut arrows")...
...or, better yet, extract the relevant subset of functionality into its own project, then just reference that whole project within the new project.
OTOH, if you want to use the existing form just as a starting point for further customization, consider...
encapsulating the original form into a custom control, then placing that control on the new form,
or visual form inheritance on a form (or even on a control from the above).
I think I would just copy the entire solution X in explorer, then open it and delete all the things that you don't want or need.
I have never been able to successfully add a Form from an existing file to a new project.
I read on a blog that you add just the *.cs file and the dependencies come in. Well, I tried this and the file did dragin and associate the *.designer and *.resx files. But, the Form icon does not display. Instead, the file looks like a normal *.cs file image. And, when I double click the file I get the code behind instead of the form object.
Is it possible to add existing Forms and get them properly recognized?
Here's an approach that doesn't involve closing the project and reopening it:
Add the 3 existing form files (cs, Designer.cs and resx).
Now, exclude the 3 files you just added from the project.
Open the Add existing item explorer window and go to your project directory.
Select the cs file and Add.
Tada. all good
After some more research I discovered the source of the issue. It is correct that all one has to import is the *.cs file. The caveat lies in the project type. If working in a Class Library project, another step must be performed.
Add a reference to System.Windows.Forms.dll and System.Drawing.
Import the *.cs file
Notes:
A. The files are only properly recognized after I performed these steps and then tried to open the file. Suddenly VS "wakes up" and fixes the files.
B. Order of the steps does not matter. If you already imported *.cs files, just fix the references.
C. If one is missing other references e.g. DevExpress or other 3rd party control imports), the *.cs files will not display properly until this has been resolved.
Sorry P.Brian.Mackey, your solution didn't work for me. It did improve it by getting VS to recognise that it was a form rather than a code file, i.e. gave it is Icon (imagine it added Form)
But only way I managed to fix the issue fully was to edit the csproj file manually in a text editor. I'm not really convinced that this is a great solution and is potentially quite dangerous, especially given I made two typing mistakes and completely broke the project but it did work once I got it right. It’s also hard to find the mistakes like not closing the tags properly or forgetting a file extention.
So the project started out with these entries after adding the files via 'Add --> Existing Item' :(P.s. I'm certain you don't have to copy the files into the project folders first, just navigate to where they are stored outside the project and VS will copy them to the folder which you right clicked on. Copy in advance of course works too.)
<Compile Include="Reports\GBudget1Report.cs">
<SubType>Form</SubType>
</Compile>
<Compile Include="Reports\GBudget1Report.Designer.cs" />
<Compile Include="Reports\GBudget2Report.cs">
<SubType>Form</SubType>
</Compile>
<Compile Include="Reports\GBudget2Report.Designer.cs" />
<Compile Include="Reports\LASHForm.cs">
<SubType>Form</SubType>
</Compile>
and further down in the file:
<EmbeddedResource Include="Reports\GBudget1Report.resx" />
<EmbeddedResource Include="Reports\GBudget2Report.resx" />
Comparing these with the existing forms in the project which were working correctly (other option is if you haven't got one, is to create a new form in Visual Studio and it'll give you the correct mark-up to copy) I discovered that the DependentUpon tag isn't associating the sub files to the main form code file.
So I edited it by hand to match:
<Compile Include="Reports\GBudget1Report.cs">
<SubType>Form</SubType>
</Compile>
<Compile Include="Reports\GBudget1Report.Designer.cs">
<DependentUpon>GBudget1Report.cs</DependentUpon>
</Compile>
<Compile Include="Reports\GBudget2Report.cs">
<SubType>Form</SubType>
</Compile>
<Compile Include="Reports\GBudget2Report.Designer.cs">
<DependentUpon>GBudget2Report.cs</DependentUpon>
</Compile>
Again further down the file:
<EmbeddedResource Include="Reports\GBudget1Report.resx">
<DependentUpon>GBudget1Report.cs</DependentUpon>
</EmbeddedResource>
<EmbeddedResource Include="Reports\GBudget2Report.resx">
<DependentUpon>GBudget2Report.cs</DependentUpon>
</EmbeddedResource>
It's not a solution I like, but it works. If anyone has any better solutions, I'm happy to listen.
You can import an existing Form into a project. The files that need to be imported depend on the version of the Visual Studio used to create the form.
I will assume that you have two separate projects, Foo and Bar, in different solutions:
C:\
Projects\
Foo\
Foo.sln
Foo.vcproj
Program.cs
Foo.cs
Foo.Designer.cs
Foo.Designer.resx
and
C:\
Projects\
Bar\
Bar.sln
Bar.vcproj
Program.cs
Bar.cs
Bar.Designer.cs
Bar.Designer.resx
Now, say that you need to import fhe form Foo to the project Bar. First, you need to copy all files that accompany Foo into the Bar project folder:
C:\
Projects\
Bar\
Bar.sln
Bar.vcproj
Program.cs
Bar.cs
Bar.Designer.cs
Bar.Designer.resx
Foo.cs
Foo.Designer.cs
Foo.Designer.resx
Then, open Bar.sln in Visual Studio and right-click on the Bar project in Solution Explorer. Select [Add existing item] and select all files that you copied for the Foo form in the dialog opened. After confirming, you should see the newly imported form correctly in Solution Explorer.
I've just encountered similar issues when upgrading VisualBasic forms, going from VisualStudio 2010 to VisualStudio 2013. There appear to be two ways to add existing items.
Problem: If I choose Main Window->Project->Add Existing Item and pull in only the file formname.vb, the result appears to be interpreted as code only (no designer), points to the original file (rather than taking a copy to the new project) and has other issues.
Solution: If instead, I go to the Solution Explorer window, click to select the project (as opposed to the lower level objects in the tree) and then right click in the window, the resulting menu offers Add->Existing Item. Using this version works as expected, requiring only that I locate the formname.vb file. No manually copying files, no pointing to mulitple files, no editing scripts, etc. I'd guess the same applies for forms written in C.
You need actually 2 files:
- Form1.cs
- Form1.Designer.cs
Copy - paste them to your new project (just make sure there is no such form with the same nameexisting in new project)
Go to solution explorer and right click on it then add existing item, here select the existing form path. Now, and this is important, on the page where you want to use existing form, you must add header file:
using "your existing project name";
If you want to create a library of windows forms it is better if you create a Windows Forms Application project. Then delete the default form (Form1), go to the project properties and change the Output Type (or project type) from Windows Forms Application to Class Library.
This way the output will be a DLL but it will have the references you need for a windows forms project. As you pointed out, when adding existing items do NOT add their corresponding .Designer and .resx files, just add their top level/main file.
Maybe it is because of using visual studio 2012, but all these solutions didn't work.
AtConway gave a hint to edit the csproj file. And that hint worked.
Open the solution with the project that you want to add your three files.
Let's assume you want to add MyForm.cs / MyForm.Designer.cs and MyForm.resX. Make sure they are in the folder of your project
Add a dummy form (or usercontrol) with a dummy name: MyTempForm.
Save the solution and close it in Developer Studio
In a windows explorer delete the three MyTempForm files
Rename your three MyForm files in MyTempForm, with the same extensions.
Open your solution again in Developer Studio 2012
See that your MyForm is now fully available as MyTempForm
In the solution explorer rename MyTempForm back to MyForm
Assume that you want to import a Form called YourFormName. Then you should only add YourFormName.cs to the project - the rest parts (YourFormName.designer.cs and YourFormName.resx) will be added automatically.
steps:
Create WinForms project (in my case .Net Framework is 4.5.1) in VS2013
Right-click on projects -> Add -> Existing Item...
copy winform you want to import to the folder of your project. If you want to add it to a new folder then first create a folder then add.
Search for any WinForm with controls (I added two forms created in VS2010 for .NET framework 4)
in lesser than 10 sec visual studio added all the remaining files and i can open this in design mode.
After trying several methods the easiest way for me to use an existing WinForm was found to be: (similar to HaraldDuch’s answer) and tested only on VS2013:
1) Before moving your existing WinForm to the destination project’s source folder, create a dummy WinForm using the same name of your source WinForm.
2) Close your VS solution while saving.
3) Delete/Replace the newly created dummy set of WinForm files (*.cs, *.Designer.cs and *.resx) from Windows Explorer (off VS IDE) with the existing WinForm files you want to use.
4) Open VS to find your existing WinForm and you can rename it from VS IDE if you wish and you will need to change the namespace of the old WinForm to match your new project.
After doing a lot of testing and failing to correctly recognise the form when added, even though .designer and .resx were copying through when .vb was imported, I found Vidar's solution the best, least hacky fix.
It appears that if these references are not already in the project (if there are no forms yet), the form is not recognised as a form and is imported as a code module instead.
System.Drawing
System.Windows.Forms
These can either be added manually per their solution above, or you can simply
Add a new blank form to the project (this automatically adds the references above)
Add existing form .vb/.cs you want to import (it will now show the form icon in the Solution Explorer and 'View Designer' will be available from context)
Delete the blank form or use it for something else
This does not require editing any of the VS config files as shown in other answers to the question.
I tried almost all of the proposed solutions but none of them really worked for me. I finally ended up editing the csproj file myself. After I added the forms from another project into my new project, I opened the csproj file and I noticed that there was a missing part to the reference that was added by Visual Studio. Therefore, I edited the node according to the following template.
<Compile Include="NewForm.cs">
<SubType>Form</SubType>
</Compile>
<Compile Include="NewForm.Designer.cs">
<DependentUpon>NewForm.cs</DependentUpon>
</Compile>
Then I restarted Visual Studio and everything worked like a charm.
In my case, I have also noted that I can only ad one form at a time. You will get to see the forms as seperate items if you try to add multiple forms at the same time.
All that is needed in visual Studio 2012 is the following:
Copy the three files for the form into the project folder (.cs, .designer.cs and .resx)
Go to the project and add an existing object.
Select the .CS file
It will import and look like a standard code file. Double-clicking on it will not open the designer as mentioned above. However just click on save all files and then close and re-open the project, now it is recognized as a form and works correctly.
You can still use "Add Existing iTem"
"Add Existing iTem", select three files (.cs .resx .Designer.cs)
make sure "namespace Application" in your .cs file is the same as the project
now you can use auto-complete the Form you just added.
This worked for me just now (I have the same problem as you).
1. Created new winform with the same name, added something to it (so the resx file is created), saved and closed.
2. Replace newly created files with your original form.
3. Done
Drag and drop .cs files from filesystem to project tree in Solution Explorer (for example):
mainForm.cs
mainForm.Designer.cs
Don't forget about references if it is not Windows Forms project.
Although this is an old post, I was having the exact same problem as #MatthewRadford had described above. My workaround for this was to only add the .CS file (do not add the .resx file), and allow visual studio to automatically generate the .resx file right after adding the .cs file.
However, I found a permanent solution. If you began to experience this problem immediately after upgrading to a new version of visual studio, it is possible that during the upgrade, Active Reports was not registered properly. The solution is to deactivate your Active Reports (using GrapeCity License Manager), uninstall Active Reports, reinstall Active Reports from scratch, and reactivate your license. You should now be able to add the ReportName.cs and ReportName.resx, as well as the Designer.cs file, all at the same time, while having visual studio correctly handle their dependencies.
Just add the form file(form.vb or form.cs) other files will be created automatically.
The simplest solution that works for me is,
Close visual studio if its open
Copy all the 3 files (.cs, .designer.cs, .resx) into your project folder where all the other forms reside too.
Now open the project using visual studio.
Build the project
Open the form by right clicking it and selecting view designer, this will generate the proper designer.cs for the form. If you don't do this sometimes it might give an error saying
InitializeComponent doesnt exist int the current context.
Now you may open and edit the .cs code file
The new form will appear like a normal form in the solution explorer here after.
All you have to is to pass the .cs file. (The code file)