.NET Compact Framework and SDE needed

Hello all,

My company is going to test the use of PDA for field automation. The software is going to be developed using VB.NET with SDE (Smart Device Extension) and .NET Compact Framework and the on PocketPC 2002.

However, the SDE and .NET CF is NO LONGER available for download. Although they'll be availble in VS.NET 2003, my company (and especially the project) can NOT wait for another 2-3 months just to develop a test application.

Is there ANY way I can get the .NET CF and SDE? I tried contacting MS, but not sure who to contact! Email send goes un-replied. Please help!

i think you can expect VS.NET 2003 by the end of the month

Really?! If this is 100% true, then definitely this is good news for me! I can talk to my PM about this.

Can you confirm this? Anybody from MS can? :D

btw , I've heard about a guy programmed a wizard that upgrades VB.NET proj to VS.NET 2003 :( .It seems that out projs need upgrade :rolleyes:

:confused: Sorry Pirate, I don't understand what you mean. Are you saying that there is a programmer that create an app. that upgrade the VB.NET to VS.NET 2003

Man, I am now confused, what to do??? If I create the server applciation that will talk to my PDA using VS.NET, then later I NEED to upgrade to VS.NET 2003??

First is the missing SDE and .NET CF, now this. Will someone tell me what is going on? Anybody who can help me in this? I have 1 week to find out about .NET availability and I am going against the Java Development team. :(

unfortunately yes , we have to upgrade VB.NET projs to VB.NET2003 .Just like when we upgrade VB6 projs to VB.NET versions !:rolleyes:

this link show you new things in VB.NET 2003 .

NOT SO!

beacuse the changes arnt that big..it will upgrade it just like going from vb 5 - 6..

Quote:

---

Originally posted by Pirate
unfortunately yes , we have to upgrade VB.NET projs to VB.NET2003 .Just like when we upgrade VB6 projs to VB.NET versions !:rolleyes:

---

Where have you heard this? This is just silly. There are new features you can use with 2003, but it isn't a requirement to upgrade your apps. The framework has built in support for this. If you have version 1.1 installed, you also still have 1.0 installed. .Net is smart enough to figure out which version of the framework your app requires and uses it. That is what is so cool about it. You can include some settings to tell the framework you perfer one over the other, or to only work with one.

Quote:

---

Man, I am now confused, what to do??? If I create the server applciation that will talk to my PDA using VS.NET, then later I NEED to upgrade to VS.NET 2003??

---

No.

http://www.fawcette.com/reports/vsli..._12_03/rudder/
http://www.fawcette.com/vsm/2002_11/...02/default.asp
http://www.fawcette.com/vsm/2002_11/...te/default.asp
http://msdn.microsoft.com/vstudio/pr...03/default.asp

There are lots of links I could give you, I just did a quick search. You need to do some research to get your questions answered. A lot of people will give you information that is based on myths and rumors, be careful, especially since this is your job. Search around and get the exact info you need. If you have to, call MS's PR department and find out who to talk to about this. They love to talk about their technologies.

Quote:

---

Is there ANY way I can get the .NET CF and SDE? I tried contacting MS, but not sure who to contact! Email send goes un-replied. Please help!

---

If you become an MSDN subscriber, you will get all that on the CD's, and be able to download it.

http://msdn.microsoft.com/vstudio/pr...03/default.asp

Quote:

---

Originally posted by Pirate
this link show you new things in VB.NET 2003 .

---

Did you look over this page ?????

I think you will need to download this utility when you get that ****in version called .NET2003.....lol

VS.NET 2003 wont be available until april when Windows.NET 2003 ships. If you are an MSDN subscriber, you will get it a little earlier.

Quote:

---

Originally posted by Pirate
Did you look over this page ?????

---

The question is "Did you look over it?"

You say:

Quote:

---

Just like when we upgrade VB6 projs to VB.NET versions

---

Your link says:

Quote:

---

It’s worth noting that upgrading from VS 2002 to VS 2003 is nothing like upgrading from VB6 to .NET. In fact, you can barely call going from VS 2002 to VS 2003 an upgrade. VS 2003 doesn't touch any of your source files at all (which is a good thing). It only makes changes to the project files.

---

The only things it changes in the project file is what framework you are targeting. Nothing more. You can go reset it back to the v1.0 framework if you wish and continue on. In the March 2003 MSDN magazine they have a couple articles about the 1.1 framework and what you can do with it. I would post a link, but they don't put the current issue of the mag online till next month.

I do know it's not like upgrading VB6 projs to .NET , but after all it is called upgrade . According to this article ,

Quote:

---

it hard to manually convert the projects and it often introduced problems.

---

I know there is no much change in the new version but MS can release these new features without reproducing the whole version !!!
I would expect that MS would release new version every year :eek: .MS, Can't YOU stick with one version for 5 years at least!!!!!:rolleyes:

I think that you miss understand what is happening. They are adding features to the framework, not changing it so it is a different version. You can still write v1 apps and v1.1 apps. If the v1.1 apps use the new features that were not in v1, then v1.1 will be required to be on the computer. If you don't use any of the new v1.1 features, then your code (as long as you set it in project properties) will run on either.

Notice that all the changes that converter makes are only config type changes, none of them have to do with the source code:

In SLN files, the 8.0 must be replaced with 7.0.
In vcproj files (and only vcproj), the 7.10 part must be replaced by 7.0.
In VB.NET or C# project files, 7.10.xxxx is replaced with 7.0.9466, where xxxx is the build number of VS.NET 7.1
Also in VB.NET and C# projects, the schema version 2.0 should be replaced with 1.0.
In RESX files, the types declared are 1.0.5000 and must be replaced with 1.0.3300.
Finally, in RESX files (binary streams), the base-64 encoded part that describes the version of the stream must change from LjAuNTAw to LjAuMzMw (basically base-64-encoded versions of 1.0.5000 and 1.0.3300 respectively)