I am working on a Xamarin.Forms project in Visual Studio and have recently got another laptop. I would like to be able to edit the project when using my work laptop so I searched online and found Visual Studio Online.
The problem is I don't know how to import my current project into the Visual Studio online to get it on the other laptop. I have tried watching tutorials but all others explain how to create a new project and couldn't find any tutorials online that explain it easily.
The first step is to sign up for Visual Studio Team Services and create a new project:
Make sure you select Team Foundation Version Control during this step.
Once the project is created, you can head over to Visual Studio and make sure you're connected to TFS (Team Foundation Server).
Open the Team Explorer panel if it isn't already open (you can find it in View->Team Explorer) and click "Connect"
Once you do that, a window will open that will allow you to sign into your Microsoft account that you used to create the TFS server. Once signed in, you can select your project and click "Connect"
Your project should open in the Team Explorer panel where you should then click "Configure Workspace"
Click "Advanced Options" and then change the Local Folder to point to the folder that contains the solution you want in source control.
Click okay and say no when it asks you if you want to get latest from source control.
You can now go to the "Pending Changes" page in the Team Explorer and click on "Detected XX add(s)" and then click "Promote" in the resulting dialog.
The final step is to add a comment and check in everything!
Your code is now in source control!
From here you can proceed like normal in setting up TFS on your new computer and getting your code from TFS!
I am using VS2015 and am connected to my TFS. However when i click Team Explorer/Builds, the "New Build Definition" button does not show up. The strange thing is this all works in VS2013. Is there a toolkit i am possibly missing or is the button hidden? Not sure what i could be overlooking for the button to not show up in one version and show up in the other...
Open page Team Foundation Server in browser. And open your project. And find tab Build.
You need to update the application VS2015.
Or open in VS TeamExplorer then Builds and:
Build Definitions -> Actions -> Security...
and configure security access control.
Make sure you have expanded the Build Definitions by clicking the triangle:
I use VS 2010 and the deploy function and to get quick access to the functionality I showed Web One Click Publish toolbar. But the toolbar is only activated when I open Web.config files or when I open Properties of a web project. When I open C# code file that toolbar is disabled. I think the functionality should be enabled independently like for example functionality Build project.
Is it something wrong in my VS installation or configuration?
I've just found that it is disabled when code file being viewed (active) does not belong to Web project (but to other one instead that cannot be published).
I'm not sure how this happened as up until this morning my Intellisense was working fine in Visual Studio.
Now, however, I have lost Intellisense in my web project's files. Also, I don't see the little toolbar at the top of the window that allows me to select objects and controls
i.e. This one:
I did notice however that Intellisense and the controls selection toolbar works in my class library.
Any idea how to fix this?
I've read somewhere about setting the Build Action of my web project files to "Compile", but I cannot find a BuildAction property anywhere.
Right click on your web project, Select "Property Pages"(Shift+F4) and Click on "Build" You will see a check box "Build Web site as part of the solution". Make sure that is checked. I would also check if there are any projects that are not loaded in your solution and also restart VS and try loading the solution once again. See if you still face this issue.
As stated in the title, I copied my DLL in Visual Studio project, set it to "content" and "copy always". Added a reference to this DLL and set it to "copy locally".
I successfully managed to instance my component to a form through code but it doesn't appear in the toolbox, really boring.
How can I solve this issue?
If I link directly the DLL project to this project it works, but now I'm treating the DLL as "external" so it's not part of the same solution of the DLL project.
I had this problem with #AndrewFinnell's solution:
There are no components in 'c:....\XXXX.dll' that can be placed on the toolbox.
So I solved with drag and drop:
open Windows explorer and navigate to the DLL
drag the DLL and drop it on Visual Studio in the Toolbox, exactly where you want your components to appear.
I also realized that some components may have compatibility issues with certain .NET Framework versions. For instance A Professional Calendar/Agenda View That You Will Use seems not to work with .NET 4.5, while it does with .NET 4.
Right-click in the toolbox.
Click "Choose Items..."
Click "Browse..."
Navigate to your DLL and click Open
Then click "Ok"
Your components should then show up
The way I found to make this working is:
Add the dll, reference it
Compile the project
Save the solution and restart visual studio
And then controls show up in toolbox (not always working, I think is a sort of visual studio bug)
Like said above,
I reference the DLL in the client project by: in Solution Explorer right click > Add Reference, at this time the custom control doesn't appear in the Toolbox.
I save it and close the client project.
I restart Visual Studio 2012 and reopen the client project. Now the custom control is in the Toolbox.
I reopen the custom control project, make some modifications and compile.
And the most important, all changes that I made in the DLL project automatically were updated in the client project without need to redo "Add Reference".
Here is what I did.
After install the net 3.5 chart download from MSDN link, I manually copied the 3.5 chart dlls to my project and refer to them. Then, from the "choose item" of toolbox, browse to the dlls and add them into toolbox. Make sure the checkbox is checked for the "chart" in the "choose item" popup.
After these, the "chart" item in the toolbox should be available and enabled for .NET 3.5 project.
NOTE
(I am using Visual Studio 2010. I think my solution should work for 2012.)
I was having this same issue. I am working in Visual Studio 2010.
My user control library is written in C# and my project I'am importing it into is in Visual Basic.
If I had the C# project in my solution, the custom user controls would show up automatically. But if I only referenced the DLL it would not load the custom user controls from the referenced library into the "Toolbox".
The above post that mentions finding the file in explorer and dragging and dropping it into the toolbox solved the problem. This is a very strange way of behaving. VB user control libraries don't require this step.
This has been an issue I have had sitting on the burner for the last 2 years.
I would up-vote the previous answer but I don't have enough rep yet.
This post could use some better tags, cause it was buried on most of my google searches.
So
Reference the user control library
Drop the DLL file into the tool box.
One question I have in regards to this is: what happens if you change the project reference to the DLL (because it moved) and not attempt to update the toolbox reference (by removing the control from the toolbox and dragging and dropping the DLL from the new location)?
I tried following the other answers (thanks to all of you!), but I got this problem and I'll let you all know how I solved it and show my custom tools in toolbar (in VS 2017).
Place the .ddl file in any Library Solution
Then I add that .ddl as reference to my needed project
Build the project and restart the Visual Studio
Then, when I look into toolbox, my custom toolbox name appears in
toolbar, when I expand that I got below message
There are no Usable controls in this group. Drag an item onto this
text to add in to toolbok
I dragged the .dll and dropped under that text and then all my custom tools appeared in my toolbox.
And add lib. to folder in your solution example solutionfolder/bin/debug and then add reference to object from this folder, finally rebuild, quit, come back, drag and drop dll from this solutionfolder/.../../ and it will probably appear.