- | rssFeed | My book on MSBuild and Team Build | Archives and Categories Tuesday, 26 March 2013

My first date with Comcast/Xfinity left me feeling used and dirty

OK seriously this is not really my first date with Comcast as I’ve been a long time customer, but it was the initial setup for a new account. While visiting my family in Florida, I decided to upgrade the internet at my parents house. They were using another ISP and the connection was very slow. This post is a story of the experience that I had after that.

Before I get into all the details of what really upsets me, let me say that when the Comcast technician left my house I would have given the setup 3 stars out of five. The reasons why I would give the 3 star rating are below. The issues here are pretty minor, I never would have blogged/tweeted about these issues as I encounter these types of things everyday.

The tech wore his shoes while going in and out of the house

At this house we, like many other foreigners, take our shoes of either outside or at the entrance. The Comcast tech did not have the respect to even ask if we cared to have shoes removed or not. He freely went in and out with his shoes on. I didn’t care enough to mention anything to him, but I did take notice of this. I know that several other companies have their techs/reps wear “booties” to ensure that there is no dirt tracked into the house. I’ve also had others simply take their shoes off after asking. Comcast should care more about the wishes of their customers to ask what the policy is at the given house.

The tech moved furniture to install the modem but never moved it back

While the tech was here, there was a dresser which was blocking the outlet. When he was installing the modem he moved the dresser and did the work necessary. When he left he didn’t care to move the dresser back. He also did not ask me if I would like to have him move the dresser back.

I found this to be extremely rude. If you go to a job and move something, it needs to be moved back to its original location before you leave. Even with this I didn’t say anything because I knew that I could simply move the item back to its original location. This is concerning for the older Comcast customers though. I know if it had been my mom or dad here alone they would have had significant issues getting that piece of furniture back in it’s original location. I am hoping that the tech which visited my home would have taken the age of my parents into consideration and moved the item back before leaving.

The tech disabled my wireless and never re-enabled it

While troubleshooting the cable modem, the tech disabled my wireless adapter on my computer. When he returned my computer to me, he had not re-enabled it. Once again, not a big deal for me as I can re-enable it quicker then I could complain to him about it. The bigger issue goes back to what if it was my parents here? If the tech disabled wireless on my dad’s notebook and returned it to him, my dad would be calling me telling me how his computer was hosed. Not a phone call I like to receive.

Comcast, please if you mess with someone’s settings have the decency to revert them back to the original settings.

For these reasons I would have given the experience 3 stars out of 5. Sure the tech did a few things to piss me off, but in the end they were small insignificant issues for me. I totally understand that for others this may not be the case, and those are the customers which Comcast needs to be more careful with.

Comcast is victimizing non-tech folks by hijacking their machines

After the tech left the house, I got back on my notebook and discovered a few really shocking things. This was the same computer the tech was using to configure the modem. I immediately took notice that there were three new shortcuts on my desktop for Xfinity. I inspected them and they looked like they were just internet shortcuts. I simply deleted them. Comcast, its my desktop not yours. Don’t litter my desktop.

After that I started up Chrome and immediately was taken to some Xfinity page. WTF, really you changed my default homepage to Xfinity? I understand you are trying to get some extra traffic to your site, but this is completely unacceptable. To top it off it was not only Chrome, it was all the browsers which I had installed on my machine. This was incredibly frustrating. Once again, what if this was my parents (or your parents perhaps)? My dad’s homepage is configured to take him to BBC Persian newspaper. My dad couldn’t figure out how to do that initially, how is he supposed to fix it after the tech left? Comcast, do you think this is OK? How would have your parents felt after this?

After further investigation, I also discovered that the search provider for my browser was changed to Xfinity. OMG this is ridiculous, what the hell else has been updated? Comcast, these are my settings on my machine. These are personal and you have no right to change these, especially with out any type of consent.

Here is the result after opening Firefox.

SNAGHTML3caa8949

Wow, you’ve got some balls to set 4 different home pages on my browser. I do agree that this is a wonderful way to drive traffic to your site. Especially for those customers who do not know how to change these.

Also take a look in the image to see what happened to my favorites.

image

I don’t use favorites that much as you can see, but there are now 8 Xfinity related favorites here. OK seriously, this getting out of hand. These are not your favorites they are mine. Do you not understand the concept that these do not belong to you?

I looked to see if there was an Xfinity/Comcast installer in Add Remove programs but there wasn’t. Comcast doesn’t even have the decency to provide a way for users to undo all the damage that they have caused without asking me. Comcast, this is the worst first date ever!

The biggest issue that I have with this is the fact that I was never given an opportunity to opt out of this. And at this point I’m not even sure if I’ve successfully reverted back to the previous state.

I’m not the only one who cares about this

Immediately as I discovered these issues I tweeted about it. What else was I supposed to do?!

image image

 

Below are some responses from those in my twitter network.

 

image image

image image

After a bit of searching around I also found many others who were similarly upset with these actions. Below are a few of the better ones.

image image

Remember when I mentioned my parents, and that they would be lost in correcting these actions. Look at these people on the Firefox forums crying for help.

image image

This could be my mom or dad, or yours. Do the Comcast execs making these decisions all have tech savvy parents that would never run into this? I find that hard to believe. You can find some other links I put together here.

Wow, its very clear that these customers do not want the homepage(s) that were set for them. I feel sorry for these guys, they sign up for a service and all of a sudden things change and they feel helpless. These are not the only two instances of this. Comcast, your customers are speaking why are you not listening?

What’s next?

At this point you might be wondering what I’m going to do about this? Am I going to cancel the account I setup for my parents? Cancel my own account in Seattle? Call to get my money back? I’m not going to be doing any of that. Since I’ll only be in Florida for this week it would be difficult to get another ISP hooked up here. More importantly I don’t hate Comcast, most of the time I don’t mind them. I’ve had their service for years  and this won’t change that.

My goals here are not to get money back (although I did have to pay $50 for this “service”) or anything like that. What I’d like is for Comcast to change their policies when setting up internet/cable services for new customers. Comcast, you must respect peoples property (both digitally and physically) more than you do today. This behavior is unacceptable and it should not continue. Minimally people need to be informed when a technician is making changes to ones machine, and have the ability to opt out of it. There should also be a mechanism for a clean rollback. I trusted your tech and did not watch over him. I know better for next time. When installing malicious software on a machine to set the home page(s) it’s clear that you are acting in Comcast’s best interest. You need to start putting customers first.

I’m especially concerned with elderly clients. If my parents had received the same treatment that I did, they would not be in a good spot. My dad’s homepage would have been changed from BBC Persian to Xfinty, his wireless would have been disabled, his dresser would have been displaced, his favorites cramped, his desktop cluttered and he would have been performing internet with Xfinity. Because of that I’ll be sharing this letter with the following.

  1. As many Comcast execs that I can find on twitter/email – I have personally witnessed how impactful it is for a customer to email a VP, now its time for me to use that technique
  2. Better Business Bureau – these types of business practices are not OK, they need to stop
  3. Federal Trade Commission – they are an advocate for the consumer, hopefully others have informed them of this previously
  4. AARP – the older community needs to be informed and protected here

If there are any Comcast guys out there you can reach me at sayed.hashimi@gmail.com or on twitter.

Sayed Ibrahim Hashimi | @SayedIHashimi | http://msbuildbook.com/

Tuesday, 26 March 2013 16:07:16 (GMT Standard Time, UTC+00:00)  #     | 
Wednesday, 06 March 2013

How to publish one web project from a solution

Today on twitter @nunofcosta asked me roughly the question “How do I publish one web project from a solution that contains many?

The issue that he is running into is that he is building from the command line and passing the following properties to msbuild.exe.

    /p:DeployOnBuild=true
    /p:PublishProfile='siteone - Web Deploy'
    /p:Password=%password%

You can read more about how to automate publishing at http://sedodream.com/2013/01/06/CommandLineWebProjectPublishing.aspx.

When you pass these properties to msbuild.exe they are known as global properties. These properties are difficult to override and are passed to every project that is built. Because of this if you have a solution with multiple web projects, when each web project is built it is passed in the same set of properties. Because of this when each project is built the publish process for that project will start and it will expect to find a file named siteone – Web Deploy.pubxml in the folder Properties\PublishProfiles\. If the file doesn’t exist the operation may fail.

Note: If you are interested in using this technique for an orchestrated publish see my comments at http://stackoverflow.com/a/14231729/105999 before doing so.

So how can we resolve this?

Let’s take a look at a sample (see links below). I have a solution, PublishOnlyOne, with the following projects.

  1. ProjA
  2. ProjB

ProjA has a publish profile named ‘siteone – Web Deploy’, ProjB does not. When trying to publish this you may try the following command line.

    msbuild.exe PublishOnlyOne.sln /p:DeployOnBuild=true /p:PublishProfile=’siteone – Web Deploy’ /p:Password=%password%

See publish-sln.cmd in the samples.

If you do this, when its time for ProjB to build it will fail because there’s no siteone – Web Deploy profile for that project. Because of this, we cannot pass DeployOnBuild. Instead here is what we need to do.

  1. Edit ProjA.csproj to define another property which will conditionally set DeployOnBuild
  2. From the command line pass in that property

 

I edited ProjA and added the following property group before the Import statements in the .csproj file.

<PropertyGroup>
  <DeployOnBuild Condition=" '$(DeployProjA)'!='' ">$(DeployProjA)</DeployOnBuild>
</PropertyGroup>

 

Here you can see that DeployOnBuild is set to whatever value DeployProjA is as long as it’s not empty. Now the revised command is:

    msbuild.exe PublishOnlyOne.sln /p:DeployProjA=true /p:PublishProfile=’siteone – Web Deploy’ /p:Password=%password%

Here instead of passing DeployOnBuild, I pass in DeployProjA which will then set DeployOnBuild. Since DeployOnBuild wasn’t passed to ProjB it will not attempt to publish.

 

You can find the complete sample at https://github.com/sayedihashimi/sayed-samples/tree/master/PublishOnlyOne.

 

Sayed Ibrahim Hashimi | @SayedIHashimi | http://msbuildbook.com/

MSDeploy | web | Web Deployment Tool | Web Development | Web Publishing Pipeline Wednesday, 06 March 2013 02:48:41 (GMT Standard Time, UTC+00:00)  #     | 
Saturday, 02 March 2013

MSDeploy: How to update app settings on publish based on the publish profile

On twitter @vishcious asked me a question related to publishing. The question was

I have a web project that I am publishing to multiple locations using Visual Studio. I have setup multiple profiles and would like to update the values for these app settings differently for each profile. How can I achieve this? I am using parameters.xml to define the MSDeploy parameters.

 

Note: If you are publishing from VS and don’t care about packaging then you can use profile specific transforms as a simpler way to achieve this result. The rest of the post here assumes you specifically want MSDeploy parameters. To learn more about profile specific transforms see my short video at http://www.youtube.com/watch?v=HdPK8mxpKEI

If you are not familiar you can create custom MSDeploy parameters when you publish/package your application by creating an XML file named parameters.xml in the root of the project. A good resource on this is Vishal’s blog post. I have  created a sample (links below) which demonstrates how to accomplish what the task. Below are the project artifacts that I’ve created to setup the parameters.

web.config

<?xml version="1.0"?>
<configuration>
  <appSettings>
    <add key="email" value="default@example.com"/>
    <add key="url" value="example.com"/>
  </appSettings>
</configuration>

Parameters.xml

<?xml version="1.0" encoding="utf-8" ?>
<parameters >

  <parameter name="email" description="description">
    <parameterEntry kind="XmlFile" 
                    scope="\\web.config$" 
                    match="/configuration/appSettings/add[@key='email']/@value" />
  </parameter>

  <parameter name="url" description="description">
    <parameterEntry kind="XmlFile" 
                    scope="\\web.config$" 
                    match="/configuration/appSettings/add[@key='url']/@value" />
  </parameter>

</parameters>

In the parameters.xml file I have defined two new MSDeploy parameters., email and url. This file should be placed in the root of the project directory and it will automatically be picked up by the web publish process. If you are familiar with this you may have noticed that I have left off the DefaultValue attribute here. More to come on that later. Now that we have our parameters defined let’s see what customizations need to be made to the publish profiles (.pubxml files).

You can override the values by populating the MsDeployDeclareParameters item list. Let’s see how to do that. When you create a publish profile in Visual Studio a .pubxml file is written to the folder Properties\PublishProfiles. These are MSBuild files and they are consumed during the build+publish operation. You can customize these files in order to fine tune the publish process. In my sample project I have two publish profiles created; siteone and sitetwo. Both of these are web profiles pointing to Azure Web Sites. In the publish profiles with the samples you will find two sets of elements; properties for publishing and  my parameter customizations. You can see the content of these profiles below, I’ve left off the MSDeploy settings for brevity. Those profiles are shown below.

siteone.pubxml

<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <!-- Web deploy settings here -->  

  <ItemGroup>
    <MsDeployDeclareParameters Include="email">
      <DefaultValue>one@email.com</DefaultValue>
    </MsDeployDeclareParameters>
    <MsDeployDeclareParameters Include="url">
      <DefaultValue>http://one.example.com/</DefaultValue>
    </MsDeployDeclareParameters>
  </ItemGroup>
</Project>

sitetwo.pubxml

<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <!-- Web Deploy settings here -->

  <ItemGroup>
    <MsDeployDeclareParameters Include="email">
      <DefaultValue>two@email.com</DefaultValue>
    </MsDeployDeclareParameters>
    <MsDeployDeclareParameters Include="url">
      <DefaultValue>http://two.example.com/</DefaultValue>
    </MsDeployDeclareParameters>
  </ItemGroup>
</Project>

In these profiles you can see that I’ve  added a usage of MSDeployDeclareParameters for both parameters in parameters.xml. In each case the value for the Include attribute is the name of the parameter (matches the name attribute in parameters.xml). Along with that I’ve declared a value for the DefaultValue metadata. This will contain the value of the parameter when it is published using that profile.

After publishing siteone the values for the app settings are below.

When publishing with sitetwo the values

 

That’s it. Now let’s move on to the comment I made previously regarding the DefaultValue attribute that I left off of the parameters.xml file.

 

DefaultValue

When you create parameters and set their values there are a few different places that these can come from including; parameters.xml, auto generated from con strings and custom declared parameters in MSBuild. Because of this the Web Publishing Pipeline has a mechanism to prioritize parameters when there are duplicates. This is facilitated by a Priority metadata value on the MSDeployDeclareParameters item list. If you want to Declare a DefaultValue inside of the parameters.xml file you can do that, but you have to be aware of the impact of that. When you add a DefaultValue parameter in parameters.xml by default those values will take precedence over the items in MSDeployDeclareParameters. Because of that you’ll have to add a Priority value. The way the Priority works is that the item with the lowest priority value for a given parameter will win. The default priority value for params from parameters.xml is –50 (defined in Microsoft.Web.Publishing.targets). Because of that we have to add priority less than –50. For example.

<ItemGroup>
  <MsDeployDeclareParameters Include="email">
    <DefaultValue>two@email.com</DefaultValue>
    <Priority>-100</Priority>
  </MsDeployDeclareParameters>
  <MsDeployDeclareParameters Include="url">
    <DefaultValue>http://two.example.com/</DefaultValue>
    <Priority>-100</Priority>
  </MsDeployDeclareParameters>
</ItemGroup>

 

In this case when I publish these values will override the default value from the parameters.xml.

 

You can see the latest version of this at https://github.com/sayedihashimi/publish-samples/tree/master/AppSettingsPerProfile.

 

Sayed Ibrahim Hashimi | @SayedIHashimi | http://msbuldbook.com

Saturday, 02 March 2013 03:36:00 (GMT Standard Time, UTC+00:00)  #     |