Teach Yourself Visual Studio® .NET 2003 in 21 Days [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Teach Yourself Visual Studio® .NET 2003 in 21 Days [Electronic resources] - نسخه متنی

Jason Beres

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید












Q&A












Q1:



You had me add a Registry entry using the Registry Editor, but the setup never used it. Why?




A1:



Although you can customize the setup to use the Registry, the main goal of the Registry Editor is to create entries for your applications at installation, not at the time your application is running.



Q2:



You mentioned that we're going to learn about the .NET Framework redistribution, but you didn't cover it. What gives?




A2:



As part of your exercises at the end of the day, you're going to download a Knowledge Base article that walks you through the deployment of the .NET runtime.



Q3:



What else is there to learn? This stuff is awesome, but the tool looks so cool, there must be more!




A3:



You are correct! When you get to Day 6, you're going to build on what you learned today and take some extra steps to really make your installations great. Remember, the concept for deployment between Windows Forms applications and ASP.NET applications is identicalyou use the same tool and have the same features. So, in two days, you just build on what you learned today.



Q4:



My company uses InstallShield to create installation packages. We're moving to .NET, but still have a lot of legacy stuff we need to install. What should we do? Should we use InstallShield or use the Visual Studio .NET installation tools?




A4:



Good question. InstallShield enables you to create merge modules, as does .NET. What you can do is create the merge modules for the legacy applications, and simply add those to a Visual Studio .NET installation project.






/ 270