Visual Studio版本之间的会话信息 [英] Session Information Between Versions of Visual Studio

查看:67
本文介绍了Visual Studio版本之间的会话信息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有人知道您是否可以在Visual Studio 2003中编写一个应用程序,然后在2010年添加新功能吗?

我们试图做的是将应用程序一点一点地升级到2010年.我们希望保持一切正常运行,并在添加新功能或模块时进行编程,然后在2010年进行编程或将页面更新到2010年,并在其侧面提供指向当前页面所在位置的链接.

我们将需要传递会话信息,而无需用户登录才能访问新内容.有谁知道这是可行的,还是知道成功完成这项工作的任何人都有提示?我查看过Google,但没有看到任何真正讨论版本之间传递会话信息的内容.而且不,我们不能使用查询字符串,因为某些信息是敏感的.

谢谢,
Carolyn

Does anyone know if you can have an application coded in Visual studio 2003 and then add new functionality in 2010?

What we are trying to do is upgrade an application to 2010 in bits and pieces. We would like to keep everything up and running and as we add new features or modules then program that in 2010 or update the page to 2010 with links on the side pointing to where the current pages resides.

We would need to pass session information and not have a user log in to access the new stuff. Does anyone know if this is doable or know anyone who has done this successfully that may have tips? I''ve looked on Google and not seen anything that really discusses passing session information between versions. And no we can''t use a query string because some of the information is sensitive.

Thanks,
Carolyn

推荐答案

为什么不将整个解决方案转移到Studio的一个版本?为此,将需要一些时间和精力(通常不会花费大量时间),但这可能是前进的最佳方法.确实没有理由在一个版本中部分维护代码,而在另一版本中部分维护其他代码(除非它们是DLL,在这种情况下应该没有关系,但在一个版本中拥有所有内容仍然更容易).
Why not transfer the entire solution to one version of Studio? It would require some time and effort to do so (not a huge amount of time usually) but that would probably be the best method going forward. There''s really no reason to maintain code partially in one version and other parts partially in another version (unless they''re DLLs, in which case it shouldn''t matter but its still easier to have everything in one version).


这篇关于Visual Studio版本之间的会话信息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆