Just a quick question.
I have Visual Studio 2010 professional edition installed at my home desktop. Can I set up Nuget server for practice or self learning?
Thanks.
You certainly can: Hosting Your Own NuGet Feeds
You could use the free MyGet.org service and focus on creating the packages and learning the commands instead.
No need to set up your own NuGet server (unless you want to learn how to set it up). MyGet is an ideal solution to jump-start your NuGet learning experience.
There is nothing stopping you from installing the server, but the fact that you are not running the most recent version of Visual Studio.
You can install and use NuGet from thier website, just download a previous version of the software.
Related
Hi I made the mistake of experimenting with an Apple Mac just before the lockdown and now im stuck with it. Now I am trying to work on a tfs project in os as both bootcamp and parallels drivers drain the battery too fast.
As TFS is not supported in visual studio for Mac I have been trying to get it to work in visual studio code. I have installed the extension, but can't get tee clc working (I think its no longer supported)
It appears that tee clc is not compatible with the latest version of oracle.
I have tried installing oracle 10 and folowing this fix here but I get an error java.lang.module.FindException: Module java.xml.bind not found
can anybody point me in the right direction. I feel like im missing something as this should not be so hard.
Is TEE clc the right tool to be using. If not how should this be done now?
Thanks
We do not have TFS source control, assume you are talking TFVC source control. You are right, it is not support with Visual Studio Mac right now. But if you are using Git, it's available in Visual Studio Mac.
More details please take a look at our official doc here-- Does Visual Studio for Mac support Team Foundation Version Control?
Unsupported workarounds for TFVC
While Visual Studio for Mac doesn't officially support TFVC, the rest
of this guide provides some workarounds to work with TFVC on macOS. If
you're using TFVC for version control today, here are some solutions
you can use to access your source code hosted in TFVC:
Option 1. Use Visual Studio Code and the Azure Repos extension, for a graphical UI
Option 2. Connect to your repo using the Team Explorer Everywhere Command Line Client (TEE-CLC)
So, Tee clc is the right tool to be using.
tee-clc (can be installed with HomeBrew), which depends on Java 6, 7,
or 8 (see How to install Java 8 on Mac -- as of this writing, Java 9
will not work.)
Make sure you have installed java 8 on your Mac machine. You could also take a look at replies in this question: Connect VS code with TFS on mac It provide step by step guide of installation and configuration.
You could use https://github.com/microsoft/team-explorer-everywhere CLI tool for TFS support on Mac, or using older JetBrains IDE with TFS plugin,
for example I am using Rider 2019.3.4 with TFS plugin(already obsolete).
Screenshot of JetBrains TFS:
Working with VS2017 Community I have written a service that works on my local machine. I followed the instruction here:
https://learn.microsoft.com/en-us/dotnet/framework/windows-services/walkthrough-creating-a-windows-service-application-in-the-component-designer
and installed it successfully using Installutil.exe (as per instructions in above link). All good.
I now want to deploy that across six servers in our organisation. In Microsoft's documentation about installing services (https://learn.microsoft.com/en-us/dotnet/framework/windows-services/how-to-install-and-uninstall-services) it says:
If you’re a developer who wants to release a Windows Service that users can install and uninstall you should use InstallShield
and links to a page that applies to VS2012 (can't post any more links as my reputation<10)
I have downloaded and installed the "Microsoft Visual Studio 2017 Installer Projects" package, which allows me to create a Setup Project. When I run it, it installs the project output correctly (i.e. copies the exe & dll files to the correct folder in Program Files) but does not create the service.
There's a detailed post about deploying services on this site (question 9021075) but when I follow those instructions I get a 1001 error on Install.
All the documentation I can find refers to earlier versions of VS or the previous Installer package, so I'm not even certain if I can do it with the software I am using.
So, with VS2017 Community using Microsoft Visual Studio 2017 Installer Projects, how to I create a stand-alone Installer to deploy a service that works correctly when installed locally using InstallUtil?
Or can I use InstallUtil on the target machines? I think I'd need to install Visual Studio on them for that, which I'd prefer not to. Is there a quicker way?
I only have 6 servers to install this on, so even some manual work-around might do.
Thank you for the responses. I now have a solution. I found InstallUtil on the Target Server (in my case it was in C:\Windows\Microsoft.NET\Framework64\v4.0.30319 but search will find it). I copied and added that to my project as content so when I now deploy it, I have InstallUtil in the same folder as my EXE.
To install, I run CMD as admin, cd to project folder and issue command:
installutil.exe myService.exe
This is a one-off task. Once the service is working, to update it I just need to stop it, upload the new myService.exe (& any DLLs) to overwrite the old ones and restart it again.
Further information about settings you're using for the serviceProcessInstaller1 and serviceInstaller1 files will be needed to debug this issue, as the 1001 error raised by the installer is a generic error.
An alternative way of doing this is to use Topshelf, which is a framework for hosting services written using the .NET framework. It simplifies the creation of services, allowing developers to create a simple console application that can be installed as a service using Topshelf. The reason for this is simple: It is far easier to debug a console application than a service. And once the application is tested and ready for production, Topshelf makes it easy to install the application as a service.
Alternatively, you could use InstallUtil.exe. It is part of the .NET Framework, so no need to install Visual Studio.
The requirements on the following page state that you need to install Visual Studio with Xamarin on your local TFS server to setup Xamarin CI builds:
https://developer.xamarin.com/guides/cross-platform/ci/intro_to_ci/
topography of the CI
This is a real pain. We have lots of developers that rely on our local TFS server, most of whom don't do any Xamarin development. As such, any changes are heavily scrutinized. This often leads to us not installing the latest VS/Xamarin releases, as it's considered too risky for this vital bit of infrastructure.
We could have a Windows build machine with VS and Xamarin installed, that is connected to a Mac build machine. We'd be free to update the Windows and Mac build machines regularly, without the fear of compromising the TFS server. Is this possible? If not, why not?
Thanks in advance.
That diagram can't be right. There is no reason why you'd need VS or Xamarin installed on your TFS app tier.
I think it's showing a simplified configuration where the Windows build agent is installed alongside the app tier. That is a supported setup but is never, ever recommended by anyone, for exactly the reasons why you don't want to do it.
The diagram is simplified. You don't need to install anything on your TFS server. What you do instead is to install a Build Agent on a separate machine or virtual machine.
The installation details for the TFS 2017 / VSTS build agent v2 can be found in the official visual studio documentation.
The procedure is similar for both TFS and VSTS, where you generate an access token in TFS/VSTS, then simply enter the url for the TFS/VSTS instance when running the build agent install script, along with the access token.
There are build agents for Windows, Linux and macOS, so it is up to you how you configure how iOS builds are made.
We are currently using StarTeam as our source control, but I am looking into alternatives. We are licensed for Team Foundation Server so I am thinking of using that as I believe it can integrate with VB6 and VS2010 Prof? (StarTeam doesn't integrate with either - at least the version we have doesn't)
Looking briefly at the features of TFS it seems there is a lot in there. To start with I just want SourceCode control. Does anyone know of a good step by step idiot's guide to setting this up? What needs to be installed where, what needs to be backed up etc, etc?
Also do I need to install anything else on my client to get VS2010 to work with it?
I don't really care about migrating the data from StarTeam but if anyone knows how this can be done I would be interested!
For your Visual Studio clients, you'll have to install Team Explorer - there's an installer on the TFS media, or you can download it separately. Each Visual Studio has to have a matching Team Explorer version installed (so if you have VS2008, you'll have to install Team Explorer for 2008), but to access later TFS servers, you generally have to install an extra update. For VB 6 (or VS2003), you'll have to use the TFS MSSCCI provider.
As to installing the server, all I'd recommend is install it somewhere first and play around with it before you install it for production use - get some familiarity with it. The install process is relatively straightforward.
I'm trying to get started with building my own webparts, planning to follow this MSDN article.
I've downloaded Visual C# 2010 Express - I'm not quite at the point where I feel comfortable dropping 1000 big ones yet, and I installed Visual Web Developer 2010 Express via the WPInstaller.
Following through the tutorial, aside from the fact that I don't get the option to create a "Web Control Library", a gap I filled with this article, I can't seem to find the sn.exe tool (or the "Visual Studio 2005 Command Prompt"!).
I know it's not quite a direct programming related question, but I can't even get the thing going yet!
Any help is appreciated.
Thanks
EDIT:-
I think I may be jumping the gun quite considerably, I wrote a simple hello world example and tried to build it but it doesn't have any references to the Microsoft.SharePoint packages and they don't appear in my lists.
Am I understanding some more research I've done (namely this) correctly, in that I have to actually have a full installation of actual SharePoint on the machine I'm developing on?
sn.exe is part of the .Net Framework SDK tools - not actually part of Visual Studio.
If you've got the SDK installed (which I think you must have if you're using VS) then it will be in a directory such as (depending on which version of .NET SDK you've got installed)
c:\program files\microsoft.net\SDK\v2.0\Bin
You can develop SharePoint web parts with VS express but you won't be able to use extensions like VSeWSS which can make your life a little easier.
You don't have develop on a machine with SharePoint installed upon - you can just copy the Microsoft.SharePoint.dll assembly from a machine with it installed on and reference it in your project.
There are pros and cons to developing on a SharePoint machine.
Its easier to get started -
especially debugging locally rather
than remote debugging.
Harder to be
sure that you're code will work a
'real server' - are you sure you
don't have any dependencies that may
not be installed.
Harder to work with
multiple versions of SharePoint (2007
WSS and MOSS and 2010 foundation,
server etc).
If you do want to work with a locally installed SharePoint then
You can install windows server OS with SharePoint and Visual Studio.
there is a hack for installing SharePoint 2007 on vista (referenced in the SO article you link to)
you can install SharePoint Foundation 2010 on Windows 7 (but I am not sure what the licensing restrictions are - is this maybe something thats given through MSDN?)
If you decide to go with the remote server installation then save yourself some grief and use virtualization such as VMWare Server, Virtual PC or Hyper-V.
If you are doing SharePoint development trying to reference the Microsoft.SharePoint namespaces you need to have SharePoint installed on the machine if you want to do things like debugging, etc. For SP 2010 you CAN install SharePoint on a Win 7 machine. For previous versions of SharePoint, you will need to setup a Server that is Server 2003 or Server 2008 (you can't install SP 2007 and earlier on client machines). Generally this is a Virtual Machine for developers.
Having said all of that, there are relatively few reasons you need SharePoint to develop a WebPart. The vast majority of the WebPart functionality is part of the System.Web.UI.WebControls.WebParts namespace. Even if I am accessing SharePoint data, I generally use the ASP.NET web part.
If you are trying to use the new SharePoint VS 2010 functionality to create Visual Web Parts, etc, then you will need to install SP 2010, since that functionality is not supported in earlier version of SharePoint.
John