IDManager

[john w]

IDManager seems a bit dated. It runs under .Net 2.0. It seems over complicated to setup. Could Instant Developer not use something more like Web Deploy to manage publishing? At any rate it seems like it could use some attention and has room to make it more user friendly.

[g.lanzi]

IDManager is an Instant Developer Foundation application, so at today it runs in .net2.0 by default.

In any case, using a more recent version of the framework is possibile for IDManager and for the Instant Developer applications too.

My I ask you is you got it configured properly or if you have some suggestions about how to make IDManager better?

[john w]

Here is a thread a few weeks back about a struggle I had with IDManager. For me it is not the easiest bit of software to install, configure and use. I do like the WebDeploy methodology used by Microsoft in Visual Studio.

viewtopic.php?f=7&t=69928

In my experience you have to set your appPool to use .Net 2.0. If you set it higher(.Net version) IDManager does not like it.

[g.lanzi]

I'll take a look at it. One of the things we're thinking for the next releases is to move to a more recent version of .NET (but nothing is confirmed yet).

[Gaby_h]

One of the things we're thinking for the next releases is to move to a more recent version of .NET (but nothing is confirmed yet).

That will be fantastic. Sometimes people ask me in what version of .Net Inde is deployed, when I say 2.0 I get a funny look.

[john w]

It will be nice if that happens, one of the comments I hear is that InDe uses old technology because of the .Net 2.0 issues

[g.lanzi]

We are thinking about the migration do 4.x, but I want to specify the .net 2.0 is just a requirements. There are a lot of 4.0 Instant Develper apps in production environment right now.

You just have to do something in the web.config and you can go with it. I tried with mine one and I was able to install a new app and doing the other operations. Modified web.config is attached :)

[john w]

Thanks for the web.config sample. I will look through it. It would be nice in my mind if you did not have to modify a file to use the .Net 4.xx framework. v2.0 was updated now many years ago, its not a recent change. Just one person's opinion and not worth more than that.

Edit: I just checked and 2.0 was released in November 2005 so its been more than a decade since its release. In the world of software development that is a long time.

[g.lanzi]

I agree that 2.0 is an old guy, but there are a lot of old production servers too :)

In any case I swear, we are keeping this upgrade in consideration.

best