NuGet package name

[MehdiK]

I guess I have raised this before but not sure about the outcome. When you go to NuGet and search for TestStack you get White, Seleno, BDDfy and FluentMVCTesting but no ConventionTests and this experience matches the auto completion experience in Visual Studio Package Manager Console.

I think we should keep the nuget package names consistent across all TestStack projects for cross-promotion and also better searchability.

We could perhaps release CT 2.0 with TestStack prefix.

[JakeGinnivan]

Yep, CT v2 fixes this

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ý19/ý09/ý2013 08:13
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Subject: [ConventionTests] NuGet package name (#33)

I guess I have raised this before but not sure about the outcome. When you go to NuGet and search for TestStack you get White, Seleno, BDDfy and FluentMVCTesting but no ConventionTests and this experience matches the auto completion experience in Visual Studio Package Manager Console.

I think we should keep the nuget package names consistent across all TestStack projects for cross-promotion and also better searchability.

We could perhaps release CT 2.0 with TestStack prefix.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33.

[MehdiK]

Awesome. Can we get V2 in the next few days please? :)

On Thu, Sep 19, 2013 at 11:55 AM, Jake Ginnivan notifications@github.comwrote:

Yep, CT v2 fixes this

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ý19/ý09/ý2013 08:13
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Subject: [ConventionTests] NuGet package name (#33)

I guess I have raised this before but not sure about the outcome. When you
go to NuGet and search for TestStack you get White, Seleno, BDDfy and
FluentMVCTesting but no ConventionTests and this experience matches the
auto completion experience in Visual Studio Package Manager Console.

I think we should keep the nuget package names consistent across all
TestStack projects for cross-promotion and also better searchability.

We could perhaps release CT 2.0 with TestStack prefix.

—
Reply to this email directly or view it on GitHub<
https://github.com/TestStack/ConventionTests/issues/33>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24721360
.

[JakeGinnivan]

V2 Shipped!

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ý19/ý09/ý2013 08:37
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

Awesome. Can we get V2 in the next few days please? :)

On Thu, Sep 19, 2013 at 11:55 AM, Jake Ginnivan notifications@github.comwrote:

Yep, CT v2 fixes this

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ?19/?09/?2013 08:13
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Subject: [ConventionTests] NuGet package name (#33)

I guess I have raised this before but not sure about the outcome. When you
go to NuGet and search for TestStack you get White, Seleno, BDDfy and
FluentMVCTesting but no ConventionTests and this experience matches the
auto completion experience in Visual Studio Package Manager Console.

I think we should keep the nuget package names consistent across all
TestStack projects for cross-promotion and also better searchability.

We could perhaps release CT 2.0 with TestStack prefix.

—
Reply to this email directly or view it on GitHub<
https://github.com/TestStack/ConventionTests/issues/33>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24721360
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24721790.

[MehdiK]

That was quick. Awesome :)

We should also release a new version of the old ConventionTests nuget that depends on TestStack.ConventionTests and redirects to it. A quick readme as part of upgrade or install telling about the new package would be good too. You can see an example of this in the old bddify project here.

[JakeGinnivan]

Migration might not be fun, they are VERY different

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ý19/ý09/ý2013 10:02
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

That was quick. Awesome :)

We should also release a new version of the old ConventionTests nuget that depends on TestStack.ConventionTests and redirects to it. A quick readme as part of upgrade or install telling about the new package would be good too. You can see an example of this in the old bddify project herehttps://github.com/TestStack/TestStack.BDDfy/tree/master/NuGet/bddify-upgrade-notice.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24725495.

[MehdiK]

Sorry, I am not sure what you mean! What is different and which migration?

On Thu, Sep 19, 2013 at 4:05 PM, Jake Ginnivan notifications@github.comwrote:

Migration might not be fun, they are VERY different

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ý19/ý09/ý2013 10:02
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

That was quick. Awesome :)

We should also release a new version of the old ConventionTests nuget that
depends on TestStack.ConventionTests and redirects to it. A quick readme as
part of upgrade or install telling about the new package would be good too.
You can see an example of this in the old bddify project here<
https://github.com/TestStack/TestStack.BDDfy/tree/master/NuGet/bddify-upgrade-notice>.

—
Reply to this email directly or view it on GitHub<
https://github.com/TestStack/ConventionTests/issues/33#issuecomment-24725495>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24732520
.

[JakeGinnivan]

Convention test v1 to v2. So migrating across might be a pain. Im not sure really.

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ý19/ý09/ý2013 13:29
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

Sorry, I am not sure what you mean! What is different and which migration?

On Thu, Sep 19, 2013 at 4:05 PM, Jake Ginnivan notifications@github.comwrote:

Migration might not be fun, they are VERY different

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ?19/?09/?2013 10:02
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

That was quick. Awesome :)

We should also release a new version of the old ConventionTests nuget that
depends on TestStack.ConventionTests and redirects to it. A quick readme as
part of upgrade or install telling about the new package would be good too.
You can see an example of this in the old bddify project here<
https://github.com/TestStack/TestStack.BDDfy/tree/master/NuGet/bddify-upgrade-notice>.

—
Reply to this email directly or view it on GitHub<
https://github.com/TestStack/ConventionTests/issues/33#issuecomment-24725495>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24732520
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24734964.

[MehdiK]

You're right about breaking changes between the two and that upgrading for
existing devs might be a pain; but we don't want to leave them there with
V1. Also devs are still going to read posts and watch videos talking about
the old ConventionTests and are going to install it. If we don't direct
them to the new one they will keep using the old one never knowing there
was a new package. This redirection is easily achieved using a nuget
dependency. Like bddify package we could also bring up a
breaking_changes.mdfile in visual studio for those who want to upgrade
to explain what's
changed and how they can upgrade their existing tests. Happy to do this
some time next week.

Thoughts?

On Thu, Sep 19, 2013 at 5:37 PM, Jake Ginnivan notifications@github.comwrote:

Convention test v1 to v2. So migrating across might be a pain. Im not sure
really.

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ý19/ý09/ý2013 13:29
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

Sorry, I am not sure what you mean! What is different and which migration?

On Thu, Sep 19, 2013 at 4:05 PM, Jake Ginnivan notifications@github.comwrote:

Migration might not be fun, they are VERY different

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ?19/?09/?2013 10:02
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com

Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

That was quick. Awesome :)

We should also release a new version of the old ConventionTests nuget
that
depends on TestStack.ConventionTests and redirects to it. A quick readme
as
part of upgrade or install telling about the new package would be good
too.
You can see an example of this in the old bddify project here<

https://github.com/TestStack/TestStack.BDDfy/tree/master/NuGet/bddify-upgrade-notice>.

—
Reply to this email directly or view it on GitHub<

https://github.com/TestStack/ConventionTests/issues/33#issuecomment-24725495>.

—
Reply to this email directly or view it on GitHub<
https://github.com/TestStack/ConventionTests/issues/33#issuecomment-24732520>

.

—
Reply to this email directly or view it on GitHub<
https://github.com/TestStack/ConventionTests/issues/33#issuecomment-24734964>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24737014
.

[JakeGinnivan]

Maybe work with Kryzstztof to do it? He knows v1 :) and he also is nuget package owner

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ý19/ý09/ý2013 14:22
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

You're right about breaking changes between the two and that upgrading for
existing devs might be a pain; but we don't want to leave them there with
V1. Also devs are still going to read posts and watch videos talking about
the old ConventionTests and are going to install it. If we don't direct
them to the new one they will keep using the old one never knowing there
was a new package. This redirection is easily achieved using a nuget
dependency. Like bddify package we could also bring up a
breaking_changes.mdfile in visual studio for those who want to upgrade
to explain what's
changed and how they can upgrade their existing tests. Happy to do this
some time next week.

Thoughts?

On Thu, Sep 19, 2013 at 5:37 PM, Jake Ginnivan notifications@github.comwrote:

Convention test v1 to v2. So migrating across might be a pain. Im not sure
really.

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ?19/?09/?2013 13:29
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

Sorry, I am not sure what you mean! What is different and which migration?

On Thu, Sep 19, 2013 at 4:05 PM, Jake Ginnivan notifications@github.comwrote:

Migration might not be fun, they are VERY different

Sent from my Windows Phone

---

From: Mehdi Khalilimailto:notifications@github.com
Sent: ?19/?09/?2013 10:02
To: TestStack/ConventionTestsmailto:ConventionTests@noreply.github.com

Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [ConventionTests] NuGet package name (#33)

That was quick. Awesome :)

We should also release a new version of the old ConventionTests nuget
that
depends on TestStack.ConventionTests and redirects to it. A quick readme
as
part of upgrade or install telling about the new package would be good
too.
You can see an example of this in the old bddify project here<

https://github.com/TestStack/TestStack.BDDfy/tree/master/NuGet/bddify-upgrade-notice>.

—
Reply to this email directly or view it on GitHub<

https://github.com/TestStack/ConventionTests/issues/33#issuecomment-24725495>.

—
Reply to this email directly or view it on GitHub<
https://github.com/TestStack/ConventionTests/issues/33#issuecomment-24732520>

.

—
Reply to this email directly or view it on GitHub<
https://github.com/TestStack/ConventionTests/issues/33#issuecomment-24734964>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24737014
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-24737841.