集成Joomla和ASP.Net网页时，存在哪些不利条件/问题? [英] What disadvantages/problems are there when integrating Joomla and ASP.Net web pages?

问题描述

我的一个朋友真的很喜欢将Joomla用作其网站的基础.他还喜欢Asp.Net具备的功能，并且可以在VB.Net中进行编码.

A friend of mine really likes using Joomla as a base for his websites. He also likes the power that Asp.Net has and can code in VB.Net.

他希望将Joomla用作母版页"，并使用Asp.Net/VB.Net/SQL Server来处理应用程序的主要业务逻辑.他正计划使用Joomla包装模块( IFrame ， joomla模块)将ASP.Net集成到Joomla网站中.

He wants to use Joomla as the "Master Page" and Asp.Net/VB.Net/SQL Server to handle the main business logic of the application. He is planning on using the Joomla Wrapper Module (an IFrame, joomla modules) to integrate the ASP.Net into the Joomla website.

Joomla将能够处理安全性(用户，角色，注册)，菜单(基于角色)，静态内容(例如关于我们"页面)，并且将通过加密的用户名& Asp.Net网页的密码(此处的示例).

Joomla will be able to handle the security (users,roles,registration), menu (based on roles), static content (e.g. About Us page) and it will pass an Encrypted Username & Password to the Asp.Net web page (example here).

该网站的目标是允许用户注册&订阅(免费或付费)服务，他们将可以自定义内容并将其下载为文件.

The goal of the website is to allow users to register & subscribe to a (free or paid) service where they will be able to customize content and download it as a file.

这样做有什么缺点?有解决方法吗?

What disadvantages are there when doing this? Are there work arounds?

我能想到的一些问题是:

Some issues that I can think of are:

1. 在iframe中单击的链接不会更改浏览器的网址，这意味着您无法为页面添加书签，并且它们也不会出现在浏览器的历史记录中.
2. 如果Asp.Net必须知道用户/角色(很有可能)，则它必须访问Joomla数据库或保留自己的用户表，该表必须与Joomla的用户同步.

我永远不会以这种方式建立新的网站，但我一直在寻找具体点，以说服我的朋友，将Joomla和Asp.Net一起使用不是一个好主意.

I would never build a new website this way, but I was looking for concrete points to convince my friend that using Joomla and Asp.Net together isn't a good idea.

推荐答案

我看不到当应用程序是ASP.net时使用Joomla有什么好处(也没有看到框架为ASP.net应用程序编码的好处)使用PHP/MySQL).

I don't see what advantage you get from using Joomla when the app is ASP.net (nor the advantage of coding an ASP.net app when the framework uses PHP/MySQL).

我不认为安全性很严格，因为您可以打开iframe并绕过Joomla安全性.然后，您要谈论将用户名/密码传递给iframe的问题-但现在您需要通过ASP.net应用再次进行验证.

I'm not convinced the security is tight because you can open iframes and bypass the Joomla security. Then you talk about passing username/password to the iframe - but now you need to validate this again through the ASP.net app.

我曾经用原始PHP编写过一个应用程序，然后使用iframe将其包含在Joomla网站中.我很快就意识到根本没有安全性，因为原始PHP不了解Joomla(尽管该应用程序对站点访问者不可见，并且仅由管理员知道).我很快将其重新编码为内置组件.

I once coded an app in raw PHP and included it in a Joomla site using iframes. I realized fairly quickly that there was basically no security because the raw PHP had no knowledge of Joomla (although the app was not visible to site visitors and only known about by admin). I quickly recoded it into a built-in component.

对我来说，这听起来像是您在应用程序的两侧重新发明了轮子 .如果您想使用Joomla，请学习如何制作组件(这非常简单)并使用PHP进行操作，或者雇用某人为您完成操作；).

To me, this sounds like you're reinventing the wheel on both sides of the app. If you want to use Joomla, either learn how to make components (it's pretty simple) and do it in PHP, or hire someone to do it for you ;).

如果PHP不是您的强项，请使用完整的ASP.net网站，如GmonC建议的那样使用CMS.即使使用一些预先构建的组件(例如 Telerik )创建自己的基本CMS，也可能比集成PHP更快.和ASP.

If PHP is not your strong point, then use a full ASP.net site, perhaps with a CMS as GmonC suggested. Even creating your own basic CMS with some pre-built components (e.g. Telerik) would probably be quicker than integrating PHP and ASP.

这篇关于集成Joomla和ASP.Net网页时，存在哪些不利条件/问题?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！