Has anybody had any hands-on experience using Devexpress ASP.NET components with Delphi Prism? At the moment I'm specifically interested in using their "Calendar and Scheduling for ASP.NET" suite.
Sharing your pros/cons, successes/failures would be greatly appreciated.
I'm looking leverage my knowledge of Delphi (and my ownership of RAD Studio).
Thanks in advance.
I know that some of our customers use Prism as a platform for the ASP.NET development. However, we do not officially support this platform and thus won't be able to help you if you run into troubles. Please also refer to
Delphi Prism - ASP.NET
Related
I worked in the past -- specifically back in 2008 to 2010-- with Silverlight applications within ASP.NET . Now in 2015 I need to develop a new 2D/3D graphical tool within ASP.NET, but I just read that Silverlight will be deprecated in the near future.
Does anyone know what is the next tool that will replace Silverlight for development of graphics and Computer-aided design in ASP.NET?
I believe silverlight is still a good option. The official end of life for Microsoft Silverlight version 5 is October 12, 2021. You have time. That isn't 'too near' really. If you are to create desktop application, you can then think of using WPF. Your silverlight experience would also help you with that and it is a pretty mature technology.
Currently I'm developing a ASP.NET mvc2 project. In that i have some dll files. I want to protect it using a obfuscator. Can any one give me some help in order to do this using Dotfuscator.Thank you.
You may see this article : Protecting your .NET applications
This article demonstrates how to use Dotfuscator which is shipped
freely with Visual Studio 2010 to protect .NET assemblies and making
the process of reverse engineering difficult.
But remember you can't 100% secure your code from de-compiling, you can only make it difficult to de-compile.
i already built some web applications using asp.net MVC 3 and they work well, and currently i am in the state of starting a new web application for a medical clinic ; but i need to have some advice if i should consider using asp.net MVC 4 beta version instead of asp.net MVC 3?
thanks in advance for any help and suggestions ?
BR
Personally I would start in MVC3 and then upgrade the project to v4 when it's RTMd. Previous versions have had some issues when migrating from Betas (altho see update below).
You can be sure, however, that as with previous version increments, a swift and easy upgrade path will be available (usually there's a project conversion tool released at the same time).
I have a project I'm working on right now, and if I get to the web layer before v4 is finished, I'll be starting in v3 first.
I suppose it does depend, however, on whether any of the new features, such as the adaptive rendering via Mobile views (or indeed the Web API), are intrinsic to your solution. Just don't release on a beta platform :)
Update July 2012
I ended up getting to the web layer of my current project before v4 RTM so decided to go to the RC release first; then the nightly nuget packages for Web API support.
Apart from editor issues (that are documented), I've found no issues, even with integrating a whitelabelling extensibility library I've written, for MVCs 1-3, that operates at a very low level.
Would I have migrated early if I'd not needed the numerous benefits that the Web API provides? Probably not.
But as it is, I'm glad I did :-)
Unless you have a specific reason to use MVC 4 (perhaps a feature that isn't in MVC 3) I would stray away from using beta software for a customer/client. Who knows what bugs/issues you'll have to work around when developing the application or when you upgrade from beta to general release.
There's a reason it's in beta.
As Mackie says.. unless you need a specific feature in MVC4, i'd stay with MVC3. MVC4 is mostly just new features, and has very few changes in the way MVC itself works.
I disagree with Mackie in his comment about "there's a reason it's in beta", in fact MVC4 is very stable and has a go-live license to allow you to use it in production code. It's just that things may still change before final, which is tied more to VS11 than how stable it is.
For my thesis I want to develop an application in ASP.NET MVC, so a few weeks ago I had to make the same decision like you. This is my conclusion:
I should advice to use MVC3 (because it's stable) for your business projects.
There are some known issues ( http://www.asp.net/whitepapers/mvc4-release-notes#_Toc303253815 ) in MVC4 beta, so it would be a waste of time to get stuck one day because of beta problems.
When the time is there you'll be able to convert MVC3 with ease to MVC4. So don't hesitate and choose for MVC3 for now. You can decide later on if you want to upgrade or not.
At the link below you'll see how to easily upgrade from MVC3 to MVC4 at this moment: http://www.asp.net/whitepapers/mvc4-release-notes#_Toc303253806
I would like to use the wonderful Ext.NET library (.dll) inside a MonoDevelop project.
Is it possible? If yes, how can I register it in my project to see the <ext:something> extension like the <asp:textbox> for standard asp.net controls?
I don't have much personal experience with Ext.NET + Mono, but I do know several community members have been successfully developing with Mono. The following search results may help track down a bit more information, see
http://www.google.ca/search?q=site%3Aforums.ext.net+mono
currently iam using .NET1.1 version in next few days i will be migrating this .NET1.1 application to .NET3.5 version...so my question is how to migrate this .NET1.1 to .NET3.5..?
How to migrate this & what precuations i need to take...? plz help
If you are using Visual Studio for your development there is an upgrade feature that takes care of quite a few things.
Here is an article on the topci that might help you. link
As #Development4.0 suggested, you could open the 1.1 sln file in VS2008 and go through the wizards. If you have multiple projects (like Web Projects, Class Library etc), then I would suggest a step-by-step approach. There will be breaking changes for sure, but I think would be minimal.