tomasmcguinness / dotnet-passbook

A .Net Library for generating Apple Passbook (Wallet) files for iOS. Please get involved by creating pull requests and opening issues!
MIT License
319 stars 117 forks source link

Passbook.Generator.Tests Incompatible with VS 2012 RC #1

Closed neelmallepally closed 12 years ago

neelmallepally commented 12 years ago

While trying to open dotnet-passbook solution with VS 2012 RC there is an error "Passbook.Generator.Tests Project is incompatible"

tomasmcguinness commented 12 years ago

Hi. Could you be a little more specific? Do you get the VS 2012 conversion wizard popup or does it just say this type of project is unsupported? I created this solution in VS 2012, so it should be okay. Could you send a screenshot of the error?

neelmallepally commented 12 years ago

My bad. The problem I got was on my personal laptop. I cloned your project this morning to my office desk and there is no issue with it. Need to check VS2012 RC on the laptop.

On Thu, Jul 5, 2012 at 2:40 AM, Tomas McGuinness < reply@reply.github.com

wrote:

Hi. Could you be a little more specific? Do you get the VS 2012 conversion wizard popup or does it just say this type of project is unsupported? I created this solution in VS 2012, so it should be okay. Could you send a screenshot of the error?


Reply to this email directly or view it on GitHub:

https://github.com/tomasmcguinness/dotnet-passbook/issues/1#issuecomment-6772280

tomasmcguinness commented 12 years ago

Okay - no problem.

rudacs commented 12 years ago

I can not open with Visual Studio 2010.

tomasmcguinness commented 12 years ago

Unfortunately, Passbook isn't compatible with VS2010.

Tomas McGuinness Check out my blog at http://www.tomasmcguinness.com Follow me on twitter http://www.twitter.com/tomasmcguinness

Date: Tue, 16 Oct 2012 06:54:12 -0700 From: notifications@github.com To: dotnet-passbook@noreply.github.com Subject: Re: [dotnet-passbook] Passbook.Generator.Tests Incompatible with VS 2012 RC (#1)

I can not open with Visual Studio 2010.

          —

          Reply to this email directly or view it on GitHub.