Asuntos Oficiales > La taberna del BIT
Windows Vista, Como Les Parece El Nuevo Nucleo?
JuanK:
--- Cita de: "Eternal Idol" ---
--- Cita de: "JuanK" --- -demasiadas, ahora es mucho mas grande y abarca muchos mas aspectos puesto que es parte del nucleo del sistema operativo
--- Fin de la cita ---
¿¿A que te referis con nucleo??
--- Fin de la cita ---
:rolleyes:
Es cierto, haciendo presicion , no me refiero al nucleo como tal ( kernel) sino a la plataforma sobre la cual se ha montado el sistema. La cual se puede decir que reemplaza a win32, sin que esto implique que win32 haya sido removido.
Eternal Idol:
--- Cita de: "JuanK" ---
--- Cita de: "Eternal Idol" ---
--- Cita de: "JuanK" --- -demasiadas, ahora es mucho mas grande y abarca muchos mas aspectos puesto que es parte del nucleo del sistema operativo
--- Fin de la cita ---
¿¿A que te referis con nucleo??
--- Fin de la cita ---
:rolleyes:
Es cierto, haciendo presicion , no me refiero al nucleo como tal ( kernel) sino a la plataforma sobre la cual se ha montado el sistema. La cual se puede decir que reemplaza a win32, sin que esto implique que win32 haya sido removido.
--- Fin de la cita ---
OK, no esta en el nucleo entonces pero:
¿Entonces no siguen siendo una serie de DLLs mas que dependen de Win32 (Kernel32.dll, Gdi32.dll, etc) sino que Win32 como legacy depende de estas DLLs? Eso es lo que entiendo de lo que decis pero no estoy del todo seguro, no me parecio que fuera asi en la version (beta 1) que probe de Vista.
Diodo:
Buscando mas informacion encontre que hay un instalador del framework 3.0
http://www.microsoft.com/downloads/details...&displaylang=en
Y extensiones para el framework 3.0 en el VS2005
http://www.microsoft.com/downloads/details...&displaylang=en
Lo raro es que advierten que no es compatible con la beta2 del vista
--- Citar ---Compatability with Windows Vista Beta2
This CTP (Community Tech Preview) is intended for users of Windows Vista build 5456, Windows XP, or Windows 2003 Server. It is not supported for users running the Windows Vista Beta 2 for .NET Framework 3.0 development. If you are using Windows Vista Beta 2 for .NET Framework 3.0 development, we recommend that you do not install this version of the CTP and instead use the Beta 2 release. The .NET Framework 3.0 June CTP runtime is a later version than the one that ships with Windows Vista Beta 2, and code that uses the .NET Framework 3.0 Beta2 will not work with this CTP.
--- Fin de la cita ---
¿Estan haciendo 2 frameworks distintos? :scream:
JuanK:
--- Cita de: "Diodo" --- Buscando mas informacion encontre que hay un instalador del framework 3.0
http://www.microsoft.com/downloads/details...&displaylang=en
Y extensiones para el framework 3.0 en el VS2005
http://www.microsoft.com/downloads/details...&displaylang=en
Lo raro es que advierten que no es compatible con la beta2 del vista
--- Citar ---Compatability with Windows Vista Beta2
This CTP (Community Tech Preview) is intended for users of Windows Vista build 5456, Windows XP, or Windows 2003 Server. It is not supported for users running the Windows Vista Beta 2 for .NET Framework 3.0 development. If you are using Windows Vista Beta 2 for .NET Framework 3.0 development, we recommend that you do not install this version of the CTP and instead use the Beta 2 release. The .NET Framework 3.0 June CTP runtime is a later version than the one that ships with Windows Vista Beta 2, and code that uses the .NET Framework 3.0 Beta2 will not work with this CTP.
--- Fin de la cita ---
¿Estan haciendo 2 frameworks distintos? :scream:
--- Fin de la cita ---
Bueno tal como lo veniamos hablando en posts de un año atras, el giro de Windows es y sera hacia la arquitectura del .NET framework, asi pues windows vista presenta el siguiente paso en la evolucion de windows que es la utilizacion de un entorno de tipos seguros y de memoria administrada.
Win32 no viene implementado como dependiente del .Net FrameWork 3.0, sino que hasta donde entiendo, y no se hasta que punto, ambos funcionan a la par como plataformas de desarrollo, el objeto de esto es desde luego que Windows Vista brinde soporte al software creado para las antiguas plataformas Win32.
A diferencia de las anteriores implementaciones de Windows, no es posible crear interfaces o subsystems Win32 a partir del .NET Framework 3.0 puesto que NO es posible generar o proporcionar las carateristcas de codigo inseguro no administrado utilizadas en la totalidad de Win32 ya que la arquitectura inherente del .NET Fx tiene un plantemamiento completamenmte diferente y el soporte para estas caracteristicas es limitado.
Extracto de http://msdn.microsoft.com/windowsvista/pro...ut/default.aspx
--- Citar ---Developer Platform Evolution
An evolution for both Win32™ and .NET Framework 3.0 (formerly WinFX) begins with Windows Vista-era advances to the .NET Framework. These two programming models will enable every developer to target the advances in Windows Vista, including improved presentation and communication subsystems, improved connectivity, and substantial advances in the core security, manageability, and reliability of Windows.
It's important to note that Windows Vista is heavily emphasizing both application compatibility (existing applications should always just run) and developer compatibility (all features are accessible through both .NET Framework 3.0 and Win32). All existing source code and programming skills apply for Windows Vista developers, whether they're C++/MFC developers or Visual Basic .NET/Windows Forms developers.
WinFX
.NET Framework 3.0 (formerly WinFX) is Windows Vista's managed-code programming model, building on and extending the .NET Framework. .NET Framework 3.0 offers both practical solutions to today's software challenges and new opportunities to create software and services not possible now. It enables both developers and designers to quickly create new applications and experiences that are more reliable and secure, visually stunning, smarter about information management, better connected, and more collaborative.
A primary goal of .NET Framework 3.0 is to make it simple for developers to build a broad variety of applications more quickly than they can today, whether they're part of a development team in a Global 100 company or in a small ISV. To do this, .NET Framework 3.0 delivers:
* A consistent programming model across all Windows Vista features
* A single, intuitive, "right way" to do common tasks
* High-level class libraries that encapsulate common tasks
* A familiar programming paradigm that builds on existing skills
* A framework that is "tool-friendly"
.NET Framework 3.0 also focuses on helping developers improve software quality. One of the largest challenges facing developers today is how to build secure, reliable, scalable, versionable, and deployable applications easily. .NET Framework 3.0 will provide a programming platform that makes it much easier for developers to deliver this kind of quality across the application lifecycle without sacrificing productivity. To do this, .NET Framework 3.0 will deliver:
* Deployment and update support that is simple for developers to understand
* Security support for common tasks that is transparent to the developer
* Default capabilities that eliminate common programming errors such as buffer overruns
.NET Framework 3.0 also begins to reduce the gap between developers and designers to enable them to create better looking, easier-to-use applications. Traditional system-level APIs like Win32 were primarily focused on the system software developer as a customer. .NET Framework 3.0 represents an opportunity to reach out to new customers, and consequently it needs to be simpler to build applications on. Since a core feature of Windows Vista is the new Windows Presentation Foundation (formerly code-named "Avalon") subsystem and the AERO shell, a core customer will become the "designer" who will help provide a rich, elegant user experience.
Windows Communication Foundation
Windows Communication Foundation (formerly code name "Indigo") is Microsoft's next-generation Web services technology, and is also exposed through WinFX. Windows Communication Foundation takes Web services to the next level by providing developers with a highly productive framework for building secure, reliable, and interoperable applications. It extends the .NET Framework 2.0 with additional functionality, enabling more than six million Visual Studio developers worldwide to build connected systems using the programming languages they already know. This results in less complexity for developers, fewer components to be managed by IT professionals, reduced training for both, and significant cost savings for the organization.
Windows Communication Foundation will radically simplify how the next generation of connected systems is built. It accomplishes this through three architectural design goals:
* Built-in support for a broad set of Web services protocols
* Implicit use of service-oriented development principles
* A single API for building connected systems
Broad Support for Web Services
Today's Web services technologies provide support for basic interoperability between applications running on different platforms. However, most of these technologies lack the ability to achieve this interoperability with guarantees for end-to-end security and reliable communication. Windows Communication Foundation delivers secure, reliable, transacted interoperability through built-in support for the WS-* specifications. For developers, this drastically reduces the amount of infrastructure code required to achieve heterogeneous interoperability. For businesses, it means the ability to interact with customers, partners, and suppliers, both within and beyond the walls of the organization, regardless of the platform they use.
Service-Oriented Design
For years, developers and organizations have struggled to build software that adapts at the speed of business. Service-oriented development principles help overcome this challenge with architectural best practices for building highly adaptable software. Windows Communication Foundation is the first programming model built from the ground up to provide implicit service-oriented application development. This enables developers to build services that are autonomous and can be versioned independently of one another, thereby reducing long-term upgrade and maintenance costs. For businesses, this facilitates an IT infrastructure that is resilient to inevitable change, and is easier to manage over time.
Windows Presentation Foundation and XAML
Windows Presentation Foundation (formerly code name "Avalon") is Microsoft's unified presentation subsystem for Windows, and is exposed through WinFX. It consists of a display engine and a managed-code framework. Windows Presentation Foundation unifies how Windows creates, displays, and manipulates documents, media, and user interface (UI), enabling developers and designers to create visually stunning, differentiated user experiences.
When it ships, scheduled for 2006, Windows Presentation Foundation will also be available on Windows XP, Windows Server 2003, and all future releases of the Windows operating system.
Windows Presentation Foundation
Windows Presentation Foundation consists of two main parts: the engine and the programming framework.
* The Windows Presentation Foundation engine. The Windows Presentation Foundation engine unifies the way developers and designers experience documents, media, and UI, providing a single runtime for browser-based experiences, forms-based applications, graphics, video, audio, and documents. Windows Presentation Foundation allows your application to unleash the full power of the graphics hardware present in modern computers, and is engineered to exploit future advances in hardware. For example, Windows Presentation Foundation's vector-based rendering engine enables applications to scale to take advantage of high-DPI monitors without requiring extra work on the part of the developer or user. Similarly, when Windows Presentation Foundation detects a video card that supports hardware acceleration, it will take advantage of it.
* The Windows Presentation Foundation framework. The Windows Presentation Foundation framework delivers solutions for media, user interface design, and documents that go well beyond what developers have today. Windows Presentation Foundation is designed for extensibility, enabling developers to create their own controls on top of the engine "from the ground up" or by subclassing existing Windows Presentation Foundation controls. Central to the framework are controls for shapes, documents, images, video, animation, 3D and "panels" in which to place controls and content. These "primitives" provide the building blocks for developing next-generation user experiences.
At the same time Microsoft introduces Windows Presentation Foundation, it will also introduce XAML, a markup language to declaratively represent user interface for Windows applications, improving the richness of the tools with which developers and designers can compose and repurpose UI. For Web developers, XAML provides a familiar UI description paradigm. XAML also enables the separation of UI design from the underlying code, enabling developers and designers to work more closely together.
Why Windows Presentation Foundation?
For businesses, Windows Presentation Foundation enables improved customer relationships and differentiated applications. It empowers businesses to create strong digital customer relationships and unique branding opportunities by providing the technology to quickly deliver visually stunning, distinctive user experiences that create an affinity with customers. Moreover, because of Windows Presentation Foundation's integration of forms, documents, video, 3D, and more, businesses can create durable user-experience solutions that integrate into customers' everyday activities.
For developers and designers, Windows Presentation Foundation provides a unified UI platform, so that they can learn a single paradigm with limitless possibilities for UI experiences. For .NET developers, its framework will be familiar, and it will ultimately reduce the number of lines of code required to deliver optimal user experiences and communication logic. For designers, Windows Presentation Foundation offers a platform that eliminates boundaries between content, media, and applications. Most importantly, Windows Presentation Foundation has been engineered so that developers and designers can work closely together synchronously to quickly deliver differentiated, connected experiences.
--- Fin de la cita ---
Mas informacion acerca del papel del .net fx 3.0
http://blogs.msdn.com/somasegar/archive/20.../09/624300.aspx
Yo creo, que al igual que las anteriores API usadas en los OS microsoft, Win32 sera reemplazada gradualmente por el .NET Fx o con lo que eso se convierta en el pasar de los años, asi que creo que a Win32 le quedan 10 -15 años de lenta agonia tal como paso con 'Win16'.
Por el momento muchas de las funcionalidades ( por no decir la inmensa mayoria del nuevo pastel) incluidas en el .net fx 3.0 no son directamente accesibles desde Win32.
Eternal Idol:
--- Cita de: "JuanK" ---Yo creo, que al igual que las anteriores API usadas en los OS microsoft, Win32 sera reemplazada gradualmente por el .NET Fx o con lo que eso se convierta en el pasar de los años, asi que creo que a Win32 le quedan 10 -15 años de lenta agonia tal como paso con 'Win16'.
Por el momento muchas de las funcionalidades ( por no decir la inmensa mayoria del nuevo pastel) incluidas en el .net fx 3.0 no son directamente accesibles desde Win32.
--- Fin de la cita ---
"It's important to note that Windows Vista is heavily emphasizing both application compatibility (existing applications should always just run) and developer compatibility (all features are accessible through both .NET Framework 3.0 and Win32)"
Si este parrafo es correcto (extraido de lo que posteaste) y se continua asi Win32 no morira jamas ya que se seguira basando todo en el mismo y .NET seguira siendo como hasta la beta 1 de Vista una capa situada por encima que depende directamente de las DLLs de toda la vida.
Navegación
[#] Página Siguiente
[*] Página Anterior
Ir a la versión completa