Re: VS2012 web app precompile
Holey schmoley! The "New" option leads the way. I haven't tried the whole process yet, but it looks like it makes sense. Thanks Stephen -- Greg On 3 October 2013 13:46, Stephen Price wrote: > Click the dropdown next to the Import and select New. Give it a name. > Then under the connection tab (which it navigates to automatically) you > can change the type of deployment to File System. > The rest should be familiar hopefully. > > > > On Thu, Oct 3, 2013 at 11:34 AM, Greg Keogh wrote: > >> Folks, before VS2012 you could right-click a web application project and >> say deploy/publish and it would precompile the app and put the results in a >> folder of your choice. You could then xcopy the contents straight over to a >> live site (I haven't done that for almost a year to the exact steps are a >> bit hazy now). >> >> In VS2012 the publish process opens a totally new dialog that forces you >> to open an Azure account and sign-up for a profile before you can publish. >> Azure is utterly irrelevant to what we're doing. >> >> In the project property pages there is still an "Output Folder" field on >> the "MSBuild Options" tab, but I've no idea where that field is used. It >> hints that I have to use msbuild from the command line, but I've never need >> to do that before. >> >> *Where on earth has the facility gone to simply precompile an app?* >> >> Greg K >> > >
Re: VS2012 web app precompile
Click the dropdown next to the Import and select New. Give it a name. Then under the connection tab (which it navigates to automatically) you can change the type of deployment to File System. The rest should be familiar hopefully. On Thu, Oct 3, 2013 at 11:34 AM, Greg Keogh wrote: > Folks, before VS2012 you could right-click a web application project and > say deploy/publish and it would precompile the app and put the results in a > folder of your choice. You could then xcopy the contents straight over to a > live site (I haven't done that for almost a year to the exact steps are a > bit hazy now). > > In VS2012 the publish process opens a totally new dialog that forces you > to open an Azure account and sign-up for a profile before you can publish. > Azure is utterly irrelevant to what we're doing. > > In the project property pages there is still an "Output Folder" field on > the "MSBuild Options" tab, but I've no idea where that field is used. It > hints that I have to use msbuild from the command line, but I've never need > to do that before. > > *Where on earth has the facility gone to simply precompile an app?* > > Greg K >
VS2012 web app precompile
Folks, before VS2012 you could right-click a web application project and say deploy/publish and it would precompile the app and put the results in a folder of your choice. You could then xcopy the contents straight over to a live site (I haven't done that for almost a year to the exact steps are a bit hazy now). In VS2012 the publish process opens a totally new dialog that forces you to open an Azure account and sign-up for a profile before you can publish. Azure is utterly irrelevant to what we're doing. In the project property pages there is still an "Output Folder" field on the "MSBuild Options" tab, but I've no idea where that field is used. It hints that I have to use msbuild from the command line, but I've never need to do that before. *Where on earth has the facility gone to simply precompile an app?* Greg K
RE: Virtual visual studio development machine – looking for some setup advice
Given I actually work on the product, I’m always blowing away Windows/VS/.NET builds and I work consistently in VMs, hosted both locally & on a remote server with 4 monitors. Some advice: 1) Don’t use Virtual PC or Virtual Server. Hyper-V is now the product to use. 2) Get Windows 8. Hyper-V is now available in client x64 builds. 3) Remote Desktop into the machine, make sure you check the “Use all my monitors for the remote session”, this will cause the thing to span all Windows. 4) Perf is much better using Remote Desktop than something like VNC because session doesn’t need send images, it basically just sends drawing instructions (as if it as was drawing locally). You’ll also better experience if you match OS versions between client/server. 5) Put your source code on a different VHD than the OS. That way, you can simply attach the VHD to any Hyper image if you want to test things on multiple OS’s. 6) On Windows 8, make sure you associate a Microsoft account to your domain login (and ditto to Office/VS 2013) – that way settings roam when you switch OSs. 7) Alternately you can automate the Windows transfers settings infrastructure to save and restore all your settings with the running of a simple command-line. The biggest perf gain you are going to see is to put money into Windows 8 (or Server 2008) and replace VPC with Hyper-V. From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Joseph Cooney Sent: Wednesday, October 2, 2013 6:17 PM To: ozDotNet Subject: Re: Virtual visual studio development machine – looking for some setup advice This is pretty much how I work (local VMs, one per client/project, or remote VM supplied by the client that I rdp into). Code is checked in frequently and VMs are backed up to external drives so in the event of hardware failure I can be back up and running quickly. On 3 Oct 2013 10:43, "Greg Harris" mailto:g...@harrisconsultinggroup.com>> wrote: Hi People, I am about to setup a new development machine for a new development project and I was after some suggestions… I want to be able to run multiple separate environments at the same time so that I can test software in these environments and just trash the environment as needed when done. Also, the same idea sounds valid for my visual studio development environment. This would give me the advantage of being able to wind back to a prior known, good stable environment as needed. This would also give some additional benefits: * Disaster recovery when on the road: If I am seeing a client on the other side of the world and my laptop dies, I can go into the local store, buy a new machine and start up a VM on the machine and I have all of my environments back again at reduced stress. * Quickly move to new physical machine as needed to get additional resources. * Separate environment for each project. * Ability to build a VM and send it to the cloud for production use. I am thinking that at any one time, I would be running VM’s for: * Stable stuff like office, file system and database * Development (Visual Studio) * Test environments (typically only one, but maybe more) I realise that I am going to need to give the physical machine a LOT MORE memory and disk (but disk is cheap, probably use an SSD, OK not cheap). The other resources should share well. My guest VPC’s will all be some form of Windows OS (both 32 and 64 bit) hosted on Win 7 Pro 64 bit. The initial concerns I have are around the user interface * UI responsiveness, I have seen on some VPC’s the mouse jitter around and it be unclear where you are pointing, this can be very disconcerting. * I tend to use two or three monitors at a time, the VPC must support this. I am thinking that I will keep as little as possible running on the host OS, so that I (almost) never need to reboot it. I have already found some useful references on the web: http://stackoverflow.com/questions/633774/optimize-development-virtual-machine http://www.andrewconnell.com/HOWTO-Squeeze-Every-Last-Drop-of-Performance-Out-of-Your-Virtual-PCs Before I go and burn a lot of time on this, I wanted to review this with the list… Questions: * Do any of you do this? * Does it work well? * What should I lookout for? * What tools should I use? I assume that the best options available for hosting my VM’s are one of: * VMWare http://www.vmware.com * Oracle Virtual Box http://www.virtualbox.org * MS Virtual PC http://www.microsoft.com/en-us/download/details.aspx?id=3702 MS Virtual PC is 2011, does that mean it is stable or they have moved on to something else? Thanks in advance for your help :-). Regards Greg Harris
RE: Virtual visual studio development machine - looking for some setup advice
Hi Greg, I work remotely in Melbourne from our head office which is based in Perth. My daily work environment is via VPN, RDP to a virtual machine hosted in Perth on Hyper V Windows 2008 R2 server. I too thought the RDP environment would be an issue with lag but surprisingly it has not been an issue. I think because all the resources (Testing Servers, Web Servers, SQL Servers etc) are based in Perth and the Perth office has a decent Upload and Download bandwidth there is not any issues. I use development tools (Visual Studio 2012 etc), Web browsers, and email clients all without issues. Where you do find an issue for RDP is video content, Adobe Photoshop and Balsamic Mockups. For these tasks I use my local machine. RDP also works great with multiple monitors, currently I am using 4. I have been trying to find a solution where RDP can take two monitors and my local machine the other two but have not been successful. With RDP its either All Monitors, 1 monitor or span monitors. The big advantages to me is that I can go anywhere in the world with an internet connection and access my development machine. I don't need to carry my laptop. I can just use any computer I find. Even osx, ipads or anything else that has RDP client. Another plus is snapshots and clones. If I want to try something and not break my machine, just create a snapshot or clone. Also if you get a beefy VM server you can add additional resources to your development machine when need. I just changed my ram from 8GB to 16GB. I also use Dropbox to sync all my work documents and code between the virtual machine and my local laptop. Just in case I find that I can't access the internet or I want to edit a file locally when lag could be an issue (adobe, balsamiq or video's). The other purpose behind dropbox is that I can create a new virtual machine or get a new laptop and sync all my work documents and also access them from anywhere. I think when I move back to the Perth office I will still keep my virtual development environment. Regards Adrian Halid From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Harris Sent: Thursday, 3 October 2013 8:44 AM To: ozDotNet Subject: Virtual visual studio development machine - looking for some setup advice Hi People, I am about to setup a new development machine for a new development project and I was after some suggestions... I want to be able to run multiple separate environments at the same time so that I can test software in these environments and just trash the environment as needed when done. Also, the same idea sounds valid for my visual studio development environment. This would give me the advantage of being able to wind back to a prior known, good stable environment as needed. This would also give some additional benefits: * Disaster recovery when on the road: If I am seeing a client on the other side of the world and my laptop dies, I can go into the local store, buy a new machine and start up a VM on the machine and I have all of my environments back again at reduced stress. * Quickly move to new physical machine as needed to get additional resources. * Separate environment for each project. * Ability to build a VM and send it to the cloud for production use. I am thinking that at any one time, I would be running VM's for: * Stable stuff like office, file system and database * Development (Visual Studio) * Test environments (typically only one, but maybe more) I realise that I am going to need to give the physical machine a LOT MORE memory and disk (but disk is cheap, probably use an SSD, OK not cheap). The other resources should share well. My guest VPC's will all be some form of Windows OS (both 32 and 64 bit) hosted on Win 7 Pro 64 bit. The initial concerns I have are around the user interface * UI responsiveness, I have seen on some VPC's the mouse jitter around and it be unclear where you are pointing, this can be very disconcerting. * I tend to use two or three monitors at a time, the VPC must support this. I am thinking that I will keep as little as possible running on the host OS, so that I (almost) never need to reboot it. I have already found some useful references on the web: http://stackoverflow.com/questions/633774/optimize-development-virtual-machine http://www.andrewconnell.com/HOWTO-Squeeze-Every-Last-Drop-of-Performance-Out-of-Your-Virtual-PCs Before I go and burn a lot of time on this, I wanted to review this with the list... Questions: * Do any of you do this? * Does it work well? * What should I lookout for? * What tools should I use? I assume that the best options available for hosting my VM's are one of: * VMWare http://www.vmware.com * Oracle Virtual Box http://www.virtualbox.org * MS Virtual PC http://www.microsoft.com/en-us/download/details.aspx?id=3702 MS Virtual PC is 2011, do
Re: Virtual visual studio development machine – looking for some setup advice
This is pretty much how I work (local VMs, one per client/project, or remote VM supplied by the client that I rdp into). Code is checked in frequently and VMs are backed up to external drives so in the event of hardware failure I can be back up and running quickly. On 3 Oct 2013 10:43, "Greg Harris" wrote: > Hi People, > > I am about to setup a new development machine for a new development > project and I was after some suggestions… > > I want to be able to run multiple separate environments at the same time > so that I can test software in these environments and just trash the > environment as needed when done. Also, the same idea sounds valid for my > visual studio development environment. This would give me the advantage of > being able to wind back to a prior known, good stable environment as > needed. > > This would also give some additional benefits: > >- Disaster recovery when on the road: If I am seeing a client on the >other side of the world and my laptop dies, I can go into the local store, >buy a new machine and start up a VM on the machine and I have all of my >environments back again at reduced stress. >- Quickly move to new physical machine as needed to get additional >resources. >- Separate environment for each project. >- Ability to build a VM and send it to the cloud for production use. > > I am thinking that at any one time, I would be running VM’s for: > >- Stable stuff like office, file system and database >- Development (Visual Studio) >- Test environments (typically only one, but maybe more) > > I realise that I am going to need to give the physical machine a LOT MORE > memory and disk (but disk is cheap, probably use an SSD, OK not cheap). > The other resources should share well. > > My guest VPC’s will all be some form of Windows OS (both 32 and 64 bit) > hosted on Win 7 Pro 64 bit. > > The initial concerns I have are around the user interface > >- UI responsiveness, I have seen on some VPC’s the mouse jitter around >and it be unclear where you are pointing, this can be very disconcerting. >- I tend to use two or three monitors at a time, the VPC must support >this. > > I am thinking that I will keep as little as possible running on the host > OS, so that I (almost) never need to reboot it. > > I have already found some useful references on the web: > > http://stackoverflow.com/questions/633774/optimize-development-virtual-machine > > http://www.andrewconnell.com/HOWTO-Squeeze-Every-Last-Drop-of-Performance-Out-of-Your-Virtual-PCs > > Before I go and burn a lot of time on this, I wanted to review this with > the list… > > Questions: > >- Do any of you do this? >- Does it work well? >- What should I lookout for? >- What tools should I use? > > I assume that the best options available for hosting my VM’s are one of: > >- VMWare http://www.vmware.com >- Oracle Virtual Box http://www.virtualbox.org >- MS Virtual PC >http://www.microsoft.com/en-us/download/details.aspx?id=3702 > > MS Virtual PC is 2011, does that mean it is stable or they have moved on > to something else? > > Thanks in advance for your help :-). > > Regards > Greg Harris >
Re: Virtual visual studio development machine – looking for some setup advice
Hi Greg, I had some experience of working in Visual Studio 2010 & 2012 in a virtualised environment (VMware based remote severs) and even though the servers were local there was always those little almost imperceptible lags (death by a thousand cuts) - it was functional, just not pleasant - esp once other VS tools were added such as R#. You’d probably be ok on locally hosted vm, esp with an SSD and 8 gb ram... It’s something I’ve been thinking of doing as well... Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Pluralsight Courses: http://bit.ly/psjasonroberts From: Greg Harris Sent: Thursday, 3 October 2013 8:43 AM To: ozDotNet Hi People, I am about to setup a new development machine for a new development project and I was after some suggestions… I want to be able to run multiple separate environments at the same time so that I can test software in these environments and just trash the environment as needed when done. Also, the same idea sounds valid for my visual studio development environment. This would give me the advantage of being able to wind back to a prior known, good stable environment as needed. This would also give some additional benefits: Disaster recovery when on the road: If I am seeing a client on the other side of the world and my laptop dies, I can go into the local store, buy a new machine and start up a VM on the machine and I have all of my environments back again at reduced stress. Quickly move to new physical machine as needed to get additional resources. Separate environment for each project. Ability to build a VM and send it to the cloud for production use. I am thinking that at any one time, I would be running VM’s for: Stable stuff like office, file system and database Development (Visual Studio) Test environments (typically only one, but maybe more) I realise that I am going to need to give the physical machine a LOT MORE memory and disk (but disk is cheap, probably use an SSD, OK not cheap). The other resources should share well. My guest VPC’s will all be some form of Windows OS (both 32 and 64 bit) hosted on Win 7 Pro 64 bit. The initial concerns I have are around the user interface UI responsiveness, I have seen on some VPC’s the mouse jitter around and it be unclear where you are pointing, this can be very disconcerting. I tend to use two or three monitors at a time, the VPC must support this. I am thinking that I will keep as little as possible running on the host OS, so that I (almost) never need to reboot it. I have already found some useful references on the web: http://stackoverflow.com/questions/633774/optimize-development-virtual-machine http://www.andrewconnell.com/HOWTO-Squeeze-Every-Last-Drop-of-Performance-Out-of-Your-Virtual-PCs Before I go and burn a lot of time on this, I wanted to review this with the list… Questions: Do any of you do this? Does it work well? What should I lookout for? What tools should I use? I assume that the best options available for hosting my VM’s are one of: VMWare http://www.vmware.com Oracle Virtual Box http://www.virtualbox.org MS Virtual PC http://www.microsoft.com/en-us/download/details.aspx?id=3702 MS Virtual PC is 2011, does that mean it is stable or they have moved on to something else? Thanks in advance for your help :-). Regards Greg Harris
Virtual visual studio development machine – looking for some setup advice
Hi People, I am about to setup a new development machine for a new development project and I was after some suggestions… I want to be able to run multiple separate environments at the same time so that I can test software in these environments and just trash the environment as needed when done. Also, the same idea sounds valid for my visual studio development environment. This would give me the advantage of being able to wind back to a prior known, good stable environment as needed. This would also give some additional benefits: - Disaster recovery when on the road: If I am seeing a client on the other side of the world and my laptop dies, I can go into the local store, buy a new machine and start up a VM on the machine and I have all of my environments back again at reduced stress. - Quickly move to new physical machine as needed to get additional resources. - Separate environment for each project. - Ability to build a VM and send it to the cloud for production use. I am thinking that at any one time, I would be running VM’s for: - Stable stuff like office, file system and database - Development (Visual Studio) - Test environments (typically only one, but maybe more) I realise that I am going to need to give the physical machine a LOT MORE memory and disk (but disk is cheap, probably use an SSD, OK not cheap). The other resources should share well. My guest VPC’s will all be some form of Windows OS (both 32 and 64 bit) hosted on Win 7 Pro 64 bit. The initial concerns I have are around the user interface - UI responsiveness, I have seen on some VPC’s the mouse jitter around and it be unclear where you are pointing, this can be very disconcerting. - I tend to use two or three monitors at a time, the VPC must support this. I am thinking that I will keep as little as possible running on the host OS, so that I (almost) never need to reboot it. I have already found some useful references on the web: http://stackoverflow.com/questions/633774/optimize-development-virtual-machine http://www.andrewconnell.com/HOWTO-Squeeze-Every-Last-Drop-of-Performance-Out-of-Your-Virtual-PCs Before I go and burn a lot of time on this, I wanted to review this with the list… Questions: - Do any of you do this? - Does it work well? - What should I lookout for? - What tools should I use? I assume that the best options available for hosting my VM’s are one of: - VMWare http://www.vmware.com - Oracle Virtual Box http://www.virtualbox.org - MS Virtual PC http://www.microsoft.com/en-us/download/details.aspx?id=3702 MS Virtual PC is 2011, does that mean it is stable or they have moved on to something else? Thanks in advance for your help :-). Regards Greg Harris
