Vulcan .Net and VO 2.8
in [Visual Objects]
|
From: Rene J. Pajaron on 19 Sep 2006 10:06 Ginny, Thanks for the clarification. Anyway, is Vulcan ready or "suitable" or whatever words for that, for mobile development? Rene Ayon kay Ginny Caughey: > Rene, > > C# Express doesn't support mobile development. You need VS 2005 Standard or > above. > > -- > Ginny > > > "Rene J. Pajaron" <rjpajaron(a)gmail.com> wrote in message > news:1158243518.508933.188280(a)k70g2000cwa.googlegroups.com... > > Phil, > > > > Very interesting indeed. Considering that with VO we can do heaps of > > things. > > > > However, all my new apps will be .Net. > > > > Better download a eval for Crossfire, I will try this with C# Express > > > > Rene > > > > Ayon kay Sherlock: > >> Rene > >> > >> snip[ In my understanding, it is a .Net mobile components that u can > >> use on > >> > any .Net development platform, including Vulcan. Correct me if i am > >> > wrong. ] > >> > >> Not sure yet... but when I can get some Vulcan time up my sleeve and I > >> can get more time using .NET .. I will let you know. The trouble is we > >> have almost unlimited VO and Web work it is difficult to stop one thing > >> to move to another thing. > >> > >> snip[ I better check this out, I believe my hands will get full on > >> mobile particularly the the GSM services. ] > >> > >> We are using Crossfire 5 in this project but Crossfire 6 is out and > >> Crossfire 6.5 to be released soon. They have done absolutely heaps in > >> whole webservices area for mobiles and WIFI, Signatture capture and > >> other connectivity across the range of handhelds on the market. > >> > >> Phil McGuinness > >> ----------------- > >
From: Ginny Caughey on 19 Sep 2006 10:18 Rene, Obviously Vulcan isn't ready or it would be released. ;-) I assume that it would be "suitable", but it's not clear if the mobile emulator and remote debugging tools will be part of the Vulcan version of Visual Studio. I think most peole will design the forms using C# or VB and Visual Studio 2005 Standard or above so they get the complete Microsoft design experience, although they would use business logic and data access code written in the Vulcan language I imagine. In any case I'd recommend VS 2005 Standard or above if you're serious about Windows Mobile development, even if you plan to use Vulcan, which integrates with the Microsoft versions of VS other than the Express ones just fine. -- Ginny "Rene J. Pajaron" <rjpajaron(a)gmail.com> wrote in message news:1158674794.833881.199790(a)e3g2000cwe.googlegroups.com... > Ginny, > > Thanks for the clarification. Anyway, is Vulcan ready or "suitable" or > whatever words for that, for mobile development? > > Rene > > Ayon kay Ginny Caughey: >> Rene, >> >> C# Express doesn't support mobile development. You need VS 2005 Standard >> or >> above. >> >> -- >> Ginny >> >> >> "Rene J. Pajaron" <rjpajaron(a)gmail.com> wrote in message >> news:1158243518.508933.188280(a)k70g2000cwa.googlegroups.com... >> > Phil, >> > >> > Very interesting indeed. Considering that with VO we can do heaps of >> > things. >> > >> > However, all my new apps will be .Net. >> > >> > Better download a eval for Crossfire, I will try this with C# Express >> > >> > Rene >> > >> > Ayon kay Sherlock: >> >> Rene >> >> >> >> snip[ In my understanding, it is a .Net mobile components that u can >> >> use on >> >> > any .Net development platform, including Vulcan. Correct me if i am >> >> > wrong. ] >> >> >> >> Not sure yet... but when I can get some Vulcan time up my sleeve and I >> >> can get more time using .NET .. I will let you know. The trouble is >> >> we >> >> have almost unlimited VO and Web work it is difficult to stop one >> >> thing >> >> to move to another thing. >> >> >> >> snip[ I better check this out, I believe my hands will get full on >> >> mobile particularly the the GSM services. ] >> >> >> >> We are using Crossfire 5 in this project but Crossfire 6 is out and >> >> Crossfire 6.5 to be released soon. They have done absolutely heaps in >> >> whole webservices area for mobiles and WIFI, Signatture capture and >> >> other connectivity across the range of handhelds on the market. >> >> >> >> Phil McGuinness >> >> ----------------- >> > >
From: Rene J. Pajaron on 19 Sep 2006 10:42 Ginny, As heard more often lately: "Vulcan will be released when ready" and obviously, the natural next question is when it is ready. Now as announced, spring or summer 2006 is very near. So it is very ready for primetime. But am not waiting for Vulcan, but VO 2.8; and .Net is next to my timetable which Vulcan is my prime tools of choice and C# (when Vulcan not suitable). So, as you have written, mobile development requires more than what C# express have. Anyway, mobile dev is more like a platform and this platform have lots of choices and sometimes mixed mobile with GSM SMS. I will targetting initially with ordinary GSM phones, and progress to more advanced cellphones and PDAs. By the way, another developers is doing this stuff and i keep pushing him to .Net. His experience is little bit of this and that. Rene Ayon kay Ginny Caughey: > Rene, > > Obviously Vulcan isn't ready or it would be released. ;-) > > I assume that it would be "suitable", but it's not clear if the mobile > emulator and remote debugging tools will be part of the Vulcan version of > Visual Studio. I think most peole will design the forms using C# or VB and > Visual Studio 2005 Standard or above so they get the complete Microsoft > design experience, although they would use business logic and data access > code written in the Vulcan language I imagine. In any case I'd recommend VS > 2005 Standard or above if you're serious about Windows Mobile development, > even if you plan to use Vulcan, which integrates with the Microsoft versions > of VS other than the Express ones just fine. > > -- > Ginny > > > "Rene J. Pajaron" <rjpajaron(a)gmail.com> wrote in message > news:1158674794.833881.199790(a)e3g2000cwe.googlegroups.com... > > Ginny, > > > > Thanks for the clarification. Anyway, is Vulcan ready or "suitable" or > > whatever words for that, for mobile development? > > > > Rene > > > > Ayon kay Ginny Caughey: > >> Rene, > >> > >> C# Express doesn't support mobile development. You need VS 2005 Standard > >> or > >> above. > >> > >> -- > >> Ginny > >> > >> > >> "Rene J. Pajaron" <rjpajaron(a)gmail.com> wrote in message > >> news:1158243518.508933.188280(a)k70g2000cwa.googlegroups.com... > >> > Phil, > >> > > >> > Very interesting indeed. Considering that with VO we can do heaps of > >> > things. > >> > > >> > However, all my new apps will be .Net. > >> > > >> > Better download a eval for Crossfire, I will try this with C# Express > >> > > >> > Rene > >> > > >> > Ayon kay Sherlock: > >> >> Rene > >> >> > >> >> snip[ In my understanding, it is a .Net mobile components that u can > >> >> use on > >> >> > any .Net development platform, including Vulcan. Correct me if i am > >> >> > wrong. ] > >> >> > >> >> Not sure yet... but when I can get some Vulcan time up my sleeve and I > >> >> can get more time using .NET .. I will let you know. The trouble is > >> >> we > >> >> have almost unlimited VO and Web work it is difficult to stop one > >> >> thing > >> >> to move to another thing. > >> >> > >> >> snip[ I better check this out, I believe my hands will get full on > >> >> mobile particularly the the GSM services. ] > >> >> > >> >> We are using Crossfire 5 in this project but Crossfire 6 is out and > >> >> Crossfire 6.5 to be released soon. They have done absolutely heaps in > >> >> whole webservices area for mobiles and WIFI, Signatture capture and > >> >> other connectivity across the range of handhelds on the market. > >> >> > >> >> Phil McGuinness > >> >> ----------------- > >> > > >
From: Ginny Caughey on 19 Sep 2006 12:09 Rene, Choosing a dev tool is really secondary in my mind to choosing a mobile platform. Gary and Phil are taking the approach that they want to support a wide variety of platforms because of the types of apps that they plan to be developing and the range of customers they are targetting, but if all your mobile users will all be on Windows Mobile or CE devices like mine, all you need is VS 2005 Standard or above. It's like deciding if all your customers will be running Windows like mine do or if it's going to be profitable to go after the percentage of potential customers who might be running something else. Windows Mobile/CE doesn't have the market dominance on mobile devices that Windows has on desktops, but for business apps particularly it's a huge and growing space. -- Ginny "Rene J. Pajaron" <rjpajaron(a)gmail.com> wrote in message news:1158676962.502134.87250(a)e3g2000cwe.googlegroups.com... > Ginny, > > As heard more often lately: "Vulcan will be released when ready" and > obviously, the natural next question is when it is ready. Now as > announced, spring or summer 2006 is very near. So it is very ready for > primetime. > > But am not waiting for Vulcan, but VO 2.8; and .Net is next to my > timetable which Vulcan is my prime tools of choice and C# (when Vulcan > not suitable). > > So, as you have written, mobile development requires more than what C# > express have. Anyway, mobile dev is more like a platform and this > platform have lots of choices and sometimes mixed mobile with GSM SMS. > I will targetting initially with ordinary GSM phones, and progress to > more advanced cellphones and PDAs. By the way, another developers is > doing this stuff and i keep pushing him to .Net. His experience is > little bit of this and that. > > Rene > > Ayon kay Ginny Caughey: >> Rene, >> >> Obviously Vulcan isn't ready or it would be released. ;-) >> >> I assume that it would be "suitable", but it's not clear if the mobile >> emulator and remote debugging tools will be part of the Vulcan version of >> Visual Studio. I think most peole will design the forms using C# or VB >> and >> Visual Studio 2005 Standard or above so they get the complete Microsoft >> design experience, although they would use business logic and data access >> code written in the Vulcan language I imagine. In any case I'd recommend >> VS >> 2005 Standard or above if you're serious about Windows Mobile >> development, >> even if you plan to use Vulcan, which integrates with the Microsoft >> versions >> of VS other than the Express ones just fine. >> >> -- >> Ginny >> >> >> "Rene J. Pajaron" <rjpajaron(a)gmail.com> wrote in message >> news:1158674794.833881.199790(a)e3g2000cwe.googlegroups.com... >> > Ginny, >> > >> > Thanks for the clarification. Anyway, is Vulcan ready or "suitable" or >> > whatever words for that, for mobile development? >> > >> > Rene >> > >> > Ayon kay Ginny Caughey: >> >> Rene, >> >> >> >> C# Express doesn't support mobile development. You need VS 2005 >> >> Standard >> >> or >> >> above. >> >> >> >> -- >> >> Ginny >> >> >> >> >> >> "Rene J. Pajaron" <rjpajaron(a)gmail.com> wrote in message >> >> news:1158243518.508933.188280(a)k70g2000cwa.googlegroups.com... >> >> > Phil, >> >> > >> >> > Very interesting indeed. Considering that with VO we can do heaps >> >> > of >> >> > things. >> >> > >> >> > However, all my new apps will be .Net. >> >> > >> >> > Better download a eval for Crossfire, I will try this with C# >> >> > Express >> >> > >> >> > Rene >> >> > >> >> > Ayon kay Sherlock: >> >> >> Rene >> >> >> >> >> >> snip[ In my understanding, it is a .Net mobile components that u >> >> >> can >> >> >> use on >> >> >> > any .Net development platform, including Vulcan. Correct me if i >> >> >> > am >> >> >> > wrong. ] >> >> >> >> >> >> Not sure yet... but when I can get some Vulcan time up my sleeve >> >> >> and I >> >> >> can get more time using .NET .. I will let you know. The trouble >> >> >> is >> >> >> we >> >> >> have almost unlimited VO and Web work it is difficult to stop one >> >> >> thing >> >> >> to move to another thing. >> >> >> >> >> >> snip[ I better check this out, I believe my hands will get full on >> >> >> mobile particularly the the GSM services. ] >> >> >> >> >> >> We are using Crossfire 5 in this project but Crossfire 6 is out and >> >> >> Crossfire 6.5 to be released soon. They have done absolutely heaps >> >> >> in >> >> >> whole webservices area for mobiles and WIFI, Signatture capture and >> >> >> other connectivity across the range of handhelds on the market. >> >> >> >> >> >> Phil McGuinness >> >> >> ----------------- >> >> > >> > >
From: Heiko Mueller on 19 Sep 2006 14:42
Hi, this isn't really an answer to your question. But after a longer absence from this newsgroup I've seen that the problems are the same as before. Here are some words about my experiences with the VOPS (Platinum Subscription): I was member of VOPS until april 2006. I have payed round about 1000 EUR. When I joined the programm the release of VULCAN was announced for november 2005 (as you can read here http://www.vulcandotnet.com/VulcanPP.htm - the complete website is only a bad joke...). So I was hopefull to get this new product in a reasonable timeframe for this 1000 Bucks. After the end of my subscription there was no VULCAN-Release and no new VO-Version. Instead of this I should have to pay more bucks to get the same things. Of course I was not willing to do this. Now I'm out of the VOPS-Newsgroups, have no access to new beta-releases and no more information about the progress of Vulcan - or simpler - I have absolutly nothing for round about 1000 EUR. I was (and be) very very disappointed about this business methods from Grafx. Ok. I understand that I cant become the 'Priority Tech Support' and such things (by the the way: why this is named 'priority'? Isn't ist the only support at all?) after my 'paying period' but I cant see why I dont have longer access to new versions and the newsgroups - I HAVE PAYED MANY BUCKS FOR THIS. After this bad experiences I deleted all the VULCAN-things from my computer and switched immedediately to MS Visual Studio / C#. I know that I'm not the only one that go this way in the last few months - this is the direct result of the GrafX way doing business. Very very sad... Conclusion: If you ever had a chance dont waste your time and money and switch directly to C# - you have really support from zillion Groups, Forums and so on and tons of code, samples and solutions which can VO/VULCAN never give. Transforming VO-Code into C# is much easier then the most of you think. All GUI Parts must be redone complete new in any case if you will use all the new .NET Classes and things in your windows... Heiko Mueller PS: First: If GrafX (Brian or whoever) read this: I'm not interested in your new releases - please delete me from your customer list. Second: English isn't my foreign language ;-) |