Upgrade to new ww.dataservices

[jen_bonnett]

What are the steps to upgrade a project to the new version?

I installed the new ww.dataservices application. Opened the project,
did a regenerate and I get 33 errors where I try to build the
application.

All are related to:Error
19 The type or namespace name 'Query' does not exist in the namespace
'WebWidgetry.SubSonic' (are you missing an assembly reference?) C:
\Documents and Settings\Administrator\My Documents\Visual Studio
2008\WebSites\WW.DataServicesTest\App_Code\Generated\NewProvider\Models
\MemberPhoto.cs 717 77 C:\...\WW.DataServicesTest\

Jennifer

[Ryan Gahl]

Hi again Jennifer...

What happens if you try to create a new project instead of regenerate against your old one?

The problem is most likely due to the fact that when we make a new version, the dlls that get put into the projects are different...

Also, it's important that if Visual Studio asks you to convert your project to .NET 3.5, you say "No". The current beta version of all this stuff only works with .NET 2.0.

Let me know how it goes with a new project.

Thanks,
Ryan

--
Ryan Gahl
Manager, Senior Software Engineer
Nth Penguin, LLC
http://www.nthpenguin.com
--
WebWidgetry.com / MashupStudio.com
Future Home of the World's First Complete Web Platform
--
Inquire: 1-920-574-2218
Blog: http://www.someElement.com
LinkedIn Profile: http://www.linkedin.com/in/ryangahl

[Jennifer Bonnett]

I was able to create a new project and get it to run.  Incidentally, the new project is ASP.NET 3.5.

Guess you should update your tutorial.

Jennifer

[zacharia...@gmail.com]

Ryan,
I am having the same exact issue. I have tried the new web site as
ASP.NET 2.0 and 3.5 and I get the same error. I had to copy the
SubSonic.dll into the bin directory to get rid of the other errors I
was getting. But I still get
" Error 30 The type or namespace name 'Query' does not exist in the

namespace 'WebWidgetry.SubSonic' (are you missing an assembly

reference?)".

This error appears in every file in my Generated folder.

Zach

> Nth Penguin, LLChttp://www.nthpenguin.com

[Ryan Gahl]

Man oh man. I just cannot replicate this. Hm. Are you setting a "Generated Namespace" value to something other than the default "SubSonic.Generated"? If not, try setting that to something else, like "test" for instance... (and do so from a new project)

[Rick Ratayczak]

I am getting this error too. I have a different generated namespace.

The code says "WebWidgetry.SubSonic.Query.WWQuery" but it can't find
this reference.

Rick

On Oct 22, 8:58 am, "Ryan Gahl" <ryan.g...@nthpenguin.com> wrote:
> Man oh man. I just cannot replicate this. Hm. Are you setting a "Generated
> Namespace" value to something other than the default "SubSonic.Generated"?
> If not, try setting that to something else, like "test" for instance... (and
> do so from a new project)
>

> On Wed, Oct 22, 2008 at 10:03 AM, zcur...@syngistic.com <

> LinkedIn Profile:http://www.linkedin.com/in/ryangahl- Hide quoted text -
>
> - Show quoted text -

[Ryan Gahl]

OK... some people are obviously able to generate just fine so this one is very annoying. I will get to town trying to reproduce it on various machine load outs and install scenarios...

Let me know if any of you that are experiencing this problem make any progress in the meantime.

[Rick Ratayczak]

Ok, here's my tests. When I got this error, it's because I tried to
generate an existing project of the earlier version. SO it is probably
a reference issue.

I Created a new website with it, and it generates, but some of the
classes are actually missing. The controller and model are only using
statements, and nothing else.

So the new project does not compile either.

Rick

> > > LinkedIn Profile:http://www.linkedin.com/in/ryangahl-Hide quoted text -

[Ryan Gahl]

typo... "...should NOT* be generating anything..."

On Wed, Oct 22, 2008 at 7:06 PM, Ryan Gahl <ryan...@nthpenguin.com> wrote:

Ah that last case could actually be because your table doesn't have a primary key. SubSonic won't generate classes in that case. It's still a bug on our part (and a known one on our current list of things to fix), in that we should be generating anything in cases like that, but my guess is that particular table in your database does not have a primary key.

[Ryan Gahl]

Ah that last case could actually be because your table doesn't have a primary key. SubSonic won't generate classes in that case. It's still a bug on our part (and a known one on our current list of things to fix), in that we should be generating anything in cases like that, but my guess is that particular table in your database does not have a primary key.

[zacharia...@gmail.com]

My tables do have primary keys and I have built this same DB into
another project using subsonic. I see the subsonic version is 2.1.
I'm totally at a loss.

Zach.

[Rick Ratayczak]

Yeah, you're right Ryan, it's no primary keys. I'm inheriting this
database from the guy who worked here before me, and I never did a
through look at it because there's 183 tables.

Rick

On Oct 23, 8:02 am, "zcur...@syngistic.com"

> > LinkedIn Profile:http://www.linkedin.com/in/ryangahl- Hide quoted text -

[Ryan Gahl]

Zach, sorry, the primary key thing was related to Rick's issues.

This Query class issue is still a mystery (clearly, though, as I mentioned, it's unique to certain conditions that must exist on certain machines - as other people are not having the issue -- which sucks because it'll be hard to locate the cause)

Anyway... at this point the best I can say (and I know this is no consolation) is that we're doing our best to figure it out. I personally will be working through the weekend on this and the other bugs that have popped up in order to try to get another release candidate on the site asap).

Sorry, Zach (and anyone else not able to get these tools to work yet)!

Sincerely,
Ryan Gahl

[Rick Ratayczak]

For me the fix was to start with a new project, not an existing one. I
think you are right Ryan, and it's probably a reference issue for the
Query Class thing.

Rick

On Oct 23, 12:35 pm, "Ryan Gahl" <ryan.g...@nthpenguin.com> wrote:
> Zach, sorry, the primary key thing was related to Rick's issues.
>
> This Query class issue is still a mystery (clearly, though, as I mentioned,
> it's unique to certain conditions that must exist on certain machines - as
> other people are not having the issue -- which sucks because it'll be hard
> to locate the cause)
>
> Anyway... at this point the best I can say (and I know this is no
> consolation) is that we're doing our best to figure it out. I personally
> will be working through the weekend on this and the other bugs that have
> popped up in order to try to get another release candidate on the site
> asap).
>
> Sorry, Zach (and anyone else not able to get these tools to work yet)!
>
> Sincerely,
> Ryan Gahl
>

> On Thu, Oct 23, 2008 at 10:02 AM, zcur...@syngistic.com <

>
>
>
> zachariahtimo...@gmail.com> wrote:
>
> > My tables do have primary keys and I have built this same DB into
> > another project using subsonic.  I see the subsonic version is 2.1.
> > I'm totally at a loss.
>

> > Zach.- Hide quoted text -