tfs - Using Team Foundation Server on a development web site -


we'd start using team foundation server keep track of versions of .aspx files. use shared drive develop on asp.net site visual studio editor.

when set our paths in team foundation server, it's between our local drive , box tfs. not ideal because doesn't push changes live our development site (separate box).

is there way check out, edit, , check in files work on appear on our shared drive on iis server? or have work on them locally , copy them server?

there several options.

  1. simple: use robocopy push files dev server local machine dev server once you've checked in changes. simple set doesn't utilise full tfs capability , potentially overwrite other devs changes on server.

  2. advanced: use automated build. if use "default" build template compile web site solution , in build output have folder contains folder called "published websites" contains need deploy code server. once have use msdeploy publish code iis

other advantages using build

  • you can run code analysis against code on each build
  • you know instantly when checks in code doesn't compile
  • you can run unit tests against code on build environment
  • to on server must check in, therefore can confident haven't published code didn't checked in source control
  • you can compile in both debug , release mode in same build, reducing risk of debug code shipping
  • you can reports on things code churn, unit test code coverage , build failures improve quality of code deliver , understand weaknesses in development workflow.
  • reduce number of times hear "it works on machine"

if you're new tfs can quite daunting. suggest set automated build nothing more build solution. can copy build output dev server. once you're comfortable start @ enhancing build. e.g. turning on code analysis easy. if you're writing unit tests should easy integrate in build. setting msdeploy takes bit more time , knowledge.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more