.net or java that is the question

shuttleR 2008-07-10 10:44:09
以前的系统一直都是CS结构,最开始是powerbuilder + oracle慢慢的转到cs +oracle(linux)下了,肯定要慢慢的把所有的PB程序都转成CS的(工程量巨大)。现在因为要开发一个简单的OA系统,所以要转到BS结构了,现在在.net和java之间犹豫,是还用.net asp但是大部分的OA好像都用java开发的而且java的框架也比较丰富.并且liunx对java的支持也比对.net的好吧,可是用java电脑里要装的开发工具太多了,如vs.net和eclipse,而且bs和cs的代码就没有办法公用了。真是头疼啊。
所以请各位达人给个意见。
...全文
85 10 打赏 收藏 转发到动态 举报
写回复
用AI写文章
10 条回复
切换为时间正序
请发表友善的回复…
发表回复
我很懒 2008-07-10
  • 打赏
  • 举报
回复
简单的说一下.net的开发速度比java快,而其也很成熟,java的安全性比.net高,不过开发成本可能要高一些
liuxiuming 2008-07-10
  • 打赏
  • 举报
回复
既然是简单的OA,用.net就挺好的。
brz97 2008-07-10
  • 打赏
  • 举报
回复
[Quote=引用 5 楼 shuttleR 的回复:]
摆脱各位给个理由啊。
[/Quote]
理由啊,楼主也知道大部分OA系统都是java做的啊
那还要什么理由啊?
简单说的话,java的安全性比.net高,不过开发成本可能要高一些
bbbbbb888888 2008-07-10
  • 打赏
  • 举报
回复
用啥无所谓,到达目的就行了,会csharp,就.net,会java就java,都会的话,看那个更熟练,那个开发的时间短呗
shuttleR 2008-07-10
  • 打赏
  • 举报
回复
摆脱各位给个理由啊。
brz97 2008-07-10
  • 打赏
  • 举报
回复
OA啊,那还是java吧
ericzhangbo1982111 2008-07-10
  • 打赏
  • 举报
回复
question
nattystyle 2008-07-10
  • 打赏
  • 举报
回复
java
xiaojing7 2008-07-10
  • 打赏
  • 举报
回复
.net
shuttleR 2008-07-10
  • 打赏
  • 举报
回复
暂时倾向于.net了:
1、能够公用一些以前的代码。
2、不要安装太多的开发工具和数据库。
3、以后bs的oa肯定要和cs的程序有代码共享。
4、以后bs的oa肯定要和cs的程序会有功能,数据交互。
5、java的界面好像挺复杂的,没弄过。
谢谢楼上的各位。
介绍CMS开发的外文PDF格式的书 What this book is about This book assumes a software designer’s perspective and presents a collection of patterns that address the content-related aspects of custom software development for advanced websites or web platforms. So what are patterns? Patterns represent good practice and suggest solutions that have worked well in many practical cases. Mined from a series of successful web projects, the patterns in this book represent the collected expertise of designers from several software development teams. Key topics in the book include content modelling and content organisation, navigation, findability, personalisation and user participation. The patterns are independent of specific tools and technologies. They focus on non-functional requirements, with the overall goal of defining a sustainable software architecture. In addition, checklists for managing a web project and for the selection of a web content management system give practical and straightforward advice. I am not going to present one specific architecture, though. The reason for this is simple enough: websites are much too heterogeneous to be designed in a uniform way. Requirements differ a lot, as do the underlying technologies. There is no point in trying to define a single all-purpose architecture. Instead, the patterns in this book should serve as a practical guide to designing your own content-related custom components for your web project. Since the patterns are independent of any specific tool or programming language, you can use them to define an architecture that matches your specific needs. This isn’t to say that you have to develop all software components yourself. Actually, you should not do so. First, you’ll probably be using a content management system. There are many systems available on the market, so it is unlikely you will have to develop your own. Second, you will probably be using frameworks for web development, such as Struts, Java Server Faces, Ruby on Rails or something else. These tools can save you a lot of work, but you will have to integrate them, and there is no question that a non-trivial site with individual requirements will also require a good deal of custom software. This is where this book can help you. The book is also meant to help you to define a sustainable architecture – one that has a lasting positive effect on your website’s system characteristics. The patterns not only seek to align code and content, but also focus on non-functional requirements. For example, the site should be fast, despite the fact that good response times can be hard to achieve, especially in the presence of personalisation. Next, maintainability is essential. Only a solid architecture can ensure that later changes to your site won’t require a large and unjustified effort. There are also other important non-functional requirements, including security, reliability and scalability. Since the patterns in this book keep an eye on these things, they can help you to design a website with an underlying high-quality software architecture.

110,025

社区成员

发帖
与我相关
我的任务
社区描述
.NET技术 C#
社区管理员
  • C#
  • Web++
  • by_封爱
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告

让您成为最强悍的C#开发者

试试用AI创作助手写篇文章吧