henrycordes.nl Report : Visit Site

Technical data of the henrycordes.nl

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host henrycordes.nl. Currently, hosted in United Kingdom and its service provider is Heart Internet Ltd .

the related websites

pearsonlongman.com movable-type.co.uk sqlservercentral.com frixo.com uk.playstation.com carbonfund.org liberkey.com 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

sign in henry cordes my thoughts exactly.... e-mail me categories ajax (10) ajax - asp.net ajax (9) asp.net (22) asp.net dynamic data (1) asp.net mvc framework (2) c# (18) crm (11) css (1) devdays (5) entlib (6) fun (2) general (1) javascript (7) jquery (4) linq (3) patterns (7) sharepoint (2) silverlight (2) sql (5) team build (3) team system (5) search include comments in search tags ajax asp.net asp.net ajax asp.net dynamic data asp.net mvc framework async builds c# crm css devdays entlib fun general javascript jquery linq patterns real-time sharepoint silverlight sql team system unittests calendar << june 2018 >> mo tu we th fr sa su 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 view posts in large calendar -- commercial blogroll robin - interaction... scott hanselman's c... scottgu's blog coding horror christian weyer dennis van de laar ronald lemmen edward bakker patrick'ssharepoint... download opml file archive 2012 december (1) february (2) 2011 april (1) 2010 december (1) september (1) may (2) april (1) february (1) 2009 november (1) october (1) june (1) april (1) march (3) february (1) january (2) 2008 november (3) october (2) september (1) august (1) july (1) june (3) may (3) april (2) march (1) february (2) january (6) 2007 december (2) october (1) august (2) june (1) may (1) april (1) march (1) 2006 november (1) october (1) august (3) may (1) march (3) january (3) 2005 december (3) november (3) october (2) september (3) august (4) july (8) disclaimer the opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway. all content on this site by henry cordes is licensed under a creative commons attribution 3.0 netherlands license . servicedefinition transform using azure sdk 1.8 published 18/12/2012 by henry in team build | team system we deploy our app using tfs teambuild. to deploy to multiple environments (dev, tst, acceptance and production) we use solutionconfiguration and config transformations . because we want to leverage .net 4.5 for multiple reasons we needed to use the azure 1.8 sdk. i noticed the servicedefinition.csdef transformation was not working as before when deploying using the 1.8 azure sdk. the .ccproj file contained the following xml: <itemgroup> <servicedefinition include="servicedefinition.csdef" /> <none include="servicedefinition.local.csdef" /> <none include="servicedefinition.development.csdef" /> <none include="servicedefinition.test.csdef" /> <none include="servicedefinition.acceptance.csdef" /> <none include="servicedefinition.release.csdef" /> <serviceconfiguration include="serviceconfiguration.cscfg" /> <none include="serviceconfiguration.local.cscfg" /> <none include="serviceconfiguration.development.cscfg" /> <none include="serviceconfiguration.test.cscfg" /> <none include="serviceconfiguration.acceptance.cscfg" /> <none include="serviceconfiguration.production.cscfg" /> <none include="serviceconfiguration.release.cscfg" /> </itemgroup> <usingtask taskname="transformxml" assemblyfile="$(msbuildextensionspath)\microsoft\visualstudio\v10.0\web\microsoft.web.publishing.tasks.dll" /> <propertygroup> <serviceconfigurationtransform>serviceconfiguration.$(azuredeployenvironment).cscfg</serviceconfigurationtransform> </propertygroup> <target name="transformserviceconfiguration" beforetargets="validateservicefiles" condition="exists('$(serviceconfigurationtransform)')"> <transformxml source="@(serviceconfiguration)" destination="%(filename)%(extension).tmp" transform="$(serviceconfigurationtransform)" /> </target> <propertygroup> <servicedefinitiontransform>servicedefinition.$(azuredeployenvironment).csdef</servicedefinitiontransform> </propertygroup> <target name="transformservicedefinition" beforetargets="validateservicefiles" condition="exists('$(servicedefinitiontransform)')"> <transformxml source="@(servicedefinition)" destination="%(filename)%(extension).tmp" transform="$(servicedefinitiontransform)" /> </target> <target name="copytransformedenvironmentconfigurationxmlbuildserver" aftertargets="afterpackagecomputeservice" condition="'$(azuredeployenvironment)'!='' and '$(isdesktopbuild)'!='true' "> <copy sourcefiles="serviceconfiguration.cscfg.tmp" destinationfiles="$(outdir)serviceconfiguration.cscfg" /> <copy sourcefiles="servicedefinition.csdef.tmp" destinationfiles="servicedefinition.build.csdef" /> </target> listing 1 as you can see in line 31 of listing 1, the servicedefinition.csdef.tmp (holds transformed xml) is copied to servicedefinition.build.csdef. cspack knew about the convention that the .build.csdef file needed to be used to create the package. the package than can be deployed to azure. when we started to use the 1.8 sdk this did not work anymore. i found the following stack overflow post describing a change in this process, but not my issue. after a lot of reading log files and studying .target files, i came to the conclusion that the convention using .build.csdef does not function anymore, instead i tried changing the destinationfiles atrribute value to “$(outdir)/servicedefinition.csdef”. that works! mind the / after $(outdir), if you do not use it the filename will be longer. so line 31 will be: <copy sourcefiles="servicedefinition.csdef.tmp" destinationfiles="$(outdir)\servicedefinition.csdef" /> listing 2 henry cordes my thoughts exactly… 4edf225a-790d-4dde-86c9-5d6b23c2e6bf|1|5.0 tweet comments (0) | permalink | post rss real-time persistent long-running connections: implementation published 22/02/2012 by henry tags: real-time , async , jquery , javascript in my previous post i wrote about how we (the robin dev-team) decided to use websync for our real-time solution. this time around i want to share how we implemented websync in robin. architecture websync server supports multiple application architectures. integrated application architecture: img 01: integrated application architecture websync the integrated architecture means that the webapplication and websync server run in the same iis pool. in azure this means you can spin up a new instance when the running instance(s) run out of resources. isolated application architecture: img 02: isolated application architecture websync the isolated architecture means that the webapplication and websync server run in separate iis application pools. at this moment in time we implemented the integrated architecture, but we are debating if we need to go for the isolated architecture, we think it is more robust and gives us the opportunity to decouple the real-time, or notification logic even more. robin deployment architecture we have the following deployment architecture: img 03: robin deployment architecture as image 03 shows we use the integrated architecture, realtime is part of our process services layer. in our frontends, api’s and background worker layers we leverage websync to do the real-time handling for us. storage provider websync needs storage, and supports the following providers out-of-the-box: sticky providers in memory provider (default) sticky sql provider stateless providers stateless sql provider azure table provider we use the stateless sql provider, because it is the fastest provider websync supports that works on azure. we already had an on premise working version that used the sticky sql provider, switching seemed the easiest. we think switching to the azure table provider will be easy and we will do this if we need it for scalability reasons, we would like to avoid this because we want the best performance possible. implementation details to use websync we had to implement a few parts: database deployment script (we do not want websync to generate the tables it needs in our production environment) c

URL analysis for henrycordes.nl

http://www.henrycordes.nl///?tag=/aspnet
http://www.henrycordes.nl///2011/04/default.aspx
http://www.henrycordes.nl///?tag=/patterns
http://www.henrycordes.nl///category/aspnet-ajax.aspx
http://www.henrycordes.nl///?tag=/general
http://www.henrycordes.nl///2008/04/default.aspx
http://www.henrycordes.nl///post/2012/12/18/servicedefinition-transform-using-azure-sdk-18.aspx#comment
mailto:?subject=servicedefinition
transform
using
azure
sdk
1.8&body=thought
you
might
like
this:
http://www.henrycordes.nl/post/2012/12/18/servicedefinition-transform-using-azure-sdk-18.aspx
http://www.henrycordes.nl///2005/08/default.aspx
http://www.henrycordes.nl///default.aspx?page=17
http://www.henrycordes.nl///default.aspx?page=10
mailto:?subject=javascript
unittest
in
build&body=thought
you
might
like
this:
http://www.henrycordes.nl/post/2011/04/25/javascript-unittest-in-build.aspx
http://www.henrycordes.nl///post/feed/2010/12/15/deploying-a-windowsservice-using-teambuild-2010.aspx
http://www.henrycordes.nl///2007/12/default.aspx
http://www.henrycordes.nl///2005/12/default.aspx

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain name: henrycordes.nl
Status: active

Registrar:
Sylconia
De Veken 207C18
1716KJ Opmeer
Netherlands

Abuse Contact:

DNSSEC: no

Domain nameservers:
ns.mainnameserver.com
ns2.mainnameserver.com

Record maintained by: NL Domain Registry

Copyright notice
No part of this publication may be reproduced, published, stored in a
retrieval system, or transmitted, in any form or by any means,
electronic, mechanical, recording, or otherwise, without prior
permission of the Foundation for Internet Domain Registration in the
Netherlands (SIDN).
These restrictions apply equally to registrars, except in that
reproductions and publications are permitted insofar as they are
reasonable, necessary and solely in the context of the registration
activities referred to in the General Terms and Conditions for .nl
Registrars.
Any use of this material for advertising, targeting commercial offers or
similar activities is explicitly forbidden and liable to result in legal
action. Anyone who is aware or suspects that such activities are taking
place is asked to inform the Foundation for Internet Domain Registration
in the Netherlands.
(c) The Foundation for Internet Domain Registration in the Netherlands
(SIDN) Dutch Copyright Act, protection of authors' rights (Section 10,
subsection 1, clause 1).

  REFERRER http://www.domain-registry.nl

  REGISTRAR Stichting Internet Domeinregistratie NL

SERVERS

  SERVER whois.domain-registry.nl

  ARGS henrycordes.nl

  PORT 43

  TYPE domain

DOMAIN

  NAME henrycordes.nl

  STATUS active

SPONSOR
Sylconia
De Veken 207C18
1716KJ Opmeer
Netherlands
Abuse Contact:
DNSSEC: no

NSERVER

  NS.MAINNAMESERVER.COM 79.170.40.2

  NS2.MAINNAMESERVER.COM 79.170.43.3

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .