ppedv Blog

[cosmin dumitru] Visendo Fax printer for Windows 7 is RTM

cosmin dumitru — Thu, 14 Jan 2010 22:41:08 GMT

We just release our Fax client support for Windows 7, that is taking advantage on huge performance improvements on printing & rendering engine of Windows 7. And also the new client have few other highlights : - import windows 7 & vista contacts - settable temporary folder - size , performance and quality optimization - signed drivers , optimized installer / uninstaller you can download it from our download place Stay tuned , for new gadgets in near future, client side fax gadget with search, send functionality, extender monitoring and reporting tools,server side automation engine, for new upcoming Visendo Fax 10. Visendo Team

[cosmin dumitru] December Visendo Xmas Gifts

cosmin dumitru — Thu, 10 Dec 2009 11:50:05 GMT

We have for December an specific Sales Marketing campaign running as follow : -On Order of 3 Visendo Products you get an new coming popConnect 10 License for free - by Ordering 3 Visendo Products you get 50% discount at cheapest one. Let us know you at sales@ppedv.de about your special needs or solutions. http://www.ppedv.de/software/visendosales.aspx For all that will subscribe to our BetaTester program for the new Visendo 10 Suite and will send us feedback we have specific offers to reward their valuable contribution to Visendo products with 1 Community Edition for free, or free or small business applications package for promotional price,and many others. english speaking users - http://www.ppedv.de/software/feedback/survey.aspx?productID=48&featureID=4&langID=en or german speaking users - http://www.ppedv.de/software/feedback/survey.aspx?productID=48&featureID=2&langID=de Visendo Team

[cosmin dumitru] Team Foundation Server support in Expression Web 3

cosmin dumitru — Mon, 14 Sep 2009 16:00:39 GMT

Expression Web 3 adds support for integration with Team Foundation Server, as one of top feature requests. Some examples of the various integration points: a) Saving a file automatically checks it out b) Adding a new UserControl or assets to a project automatically adds them to source control c) Renaming or deleting files automatically renames or deletes items under source control d) Right clicking on an item that has been modified under source control allows you to submit that particular change e) View history, get latest versions of files or specific versions, undo changes, etc. To enable source control for a solution open inside Blend, the solution must be bound and residing in a valid workspace on the client. You can refer to the Visual Studio documentation on how to setup a solution under TFS source control here. While you don't need to have Visual Studio 2008 installed on the machine to avail TFS support inside Web and Blend, you do need to install Visual Studio Team System 2008 Team Explorer, a free download. You also need to install SP1 of Team Explorer, and a hotfix for Team Explorer SP1 that enables TFS support inside Web - you can download that from here. Enjoy!

[cosmin dumitru] Application hosting on Windows 2008 Core part 2

cosmin dumitru — Sun, 01 Feb 2009 17:40:02 GMT

Microsoft is working on official version of .NET and PowerShell for Server Core R2 installations, the instructions you can use at your own risk, etc., etc. The problem is that it only ships with traditional cmd.exe and not PowerShell. To make things worse neither PowerShell nor .NET as they are today can be installed on such systems. Alex Kibkalo and a great post by Artem Pronichkin on installing .NET on Server Core that makes this task easier. Basically the whole procedure consists of just four main steps: Installing Visual C++ Redistributable Packages (required for .NET). Installing .NET 2.0 SP1 Installing PowerShell. There it is :” :c:"Windows"System32"WindowsPowerShell"v1.0"powershell.exe” 1. Microsoft Visual C++ 2005 SP1 Redistributable Packages After that, copy these files to your Server Core computer and simply run them there. If your Server Core is 32-bit - just run vcredist_x86.exe. If it is 64-bit, you need to install both x86 and x64 versions (vcredist_x86.exe and vcredist_x64.exe). 2. .NET Framework This is the most tricky part. PowerShell needs .NET 2.0 and .NET 2.0 is supposed to be a component of Windows Server 2008 so we will have to get a package of the framework which can get installed on such a system. To accomplish that we will: Download .NET Framework 3.5. Unpack the setup to get access to the .NET 2.0 Service Pack 1 installation files. Download and install the Orca MSI editor. Use Orca to remove the Windows version check. Run the updated MSI. 2.1. Download .NET: Go to Microsoft’s web site and download full redistributable package of .NET 3.5. 2.2. Unpack the file: a. Create a folder c:"deploy b. Save the downloaded .NET framework package to this folder. c. Download the wonderful deploy.cmd script which Artem has posted and put it into the same folder. d. Run the script. After the script executes, the C:"Deploy"AIP folder will have both NetFx20_x64 and NetFx20_x86 folders with .NET 2.0 framework files you need. 2.3. Install Orca: This is great but unfortunately you cannot just install the files because the MSIs are specifically checking for Windows version. So now we need to disable this check. To do this we will use Microsoft’s Orca MSI editor. Note: This all needs to be done on a regular, not Server Core, machine. We will copy the results of our Orca operations to the Core box later on. If you don’t have Orca, follow these steps to download it: a. Download the Windows SDK for Windows Server 2008 and .NET Framework 3.5 installer. b. Run the installer and deselect everything except Win32 Developer Tools (this will make sure that you only download the few megs you need.) c. After the installation completes, go to C:"Program Files"Microsoft SDKs"Windows"v6.1"Bin and install Orca.msi. 2.4. Tweak the setup: Now its time to do some patching. a. Start Orca and open the MSI you need (C:"Deploy"AIP"NetFx20_x86"NetFx20a_x86.msi for 32-bit version or C:"Deploy"AIP"NetFx20_x64"NetFx20a_x64.msi for x64). b. Click Component. c. In x86 locate: Regtlib.exe_Tool_____X86.3643236F_FC70_11D3_A536_0090278A1BB8 In x64 locate that one and Regtlib.exe_Tool_____A64.3643236F_FC70_11D3_A536_0090278A1BB8 d. Change the Condition from (VersionNT < 600) or Version9X to just VersionNT or Version9X. e. Save changes (either to that same MSI or a transform file.) 2.5. Install .NET Copy the files (the whole folder) to your core machine and start the MSI via this command line (note that you need to use msiexec in order to pass the vsextui=1 parameter): If you saved a transformed file and are running 64-bit version you will probably run: %SystemRoot%"system32"msiexec.exe /package "NetFx20_x64"NetFx20a_x64.msi" vsextui=1 transforms="ServerCore.mst" On x86 without a transform that would be: %SystemRoot%"system32"msiexec.exe /package "NetFx20_x86"NetFx20a_x86.msi" vsextui=1 That’s it. Now we have .NET installed and can go to the final step - PowerShell installation! 3. Windows PowerShell There is no PowerShell v1 setup for Windows 2008 (again, because it is supposed to be a component) but you can actually download and install the CTP (note: this is a pre-beta code - not for production use). PowerShell v2 CTP2 is available from Microsoft’s downloads page. Download the version you need, copy the msi over to the Server Core box and simply run the msi. 4. Now you can start PowerShell! Just run: c:"Windows"System32"WindowsPowerShell"v1.0"powershell.exe And you will see the prompt change to: PS C:> That’s it. Now you are among the first geeks in the Universe to have PowerShell on Server Core!

[cosmin dumitru] Application hosting on Windows 2008 Core part 1

cosmin dumitru — Sun, 01 Feb 2009 17:15:54 GMT

Windows 2008 Core , cool server platform, tiny efficient and secure, all opinions about it are great even from the Linux guys (they love the console). But now from the application development life cycle what we can deploy on it and how ? that were my questions before hosting and migrate our Fax Services to the new Virtualized Environment. Benefits of a Server Core installation The Server Core installation option of Windows Server 2008 provides the following benefits: Reduced maintenance. Because the Server Core installation option installs only what is required to have a manageable server for the AD DS, AD LDS, DHCP Server, DNS Server, File Services, Print Services, and Streaming Media Services roles, less maintenance is required than on a full installation of Windows Server 2008. Reduced attack surface. Because Server Core installations are minimal, there are fewer applications running on the server, which decreases the attack surface. Reduced management. Because fewer applications and services are installed on a server running the Server Core installation, there is less to manage. Less disk space required. A Server Core installation requires only about 1 gigabyte (GB) of disk space to install and approximately 2 GB for operations after the installation. Quick Overview : Step 1 – Windows 2008 Server Core Configurator After installation are few task need it ,to get the machine in the network infrastructure and working environment, for who is not used with WSH scripts and command line tools, some guys from Microsoft build an tool : http://blogs.microsoft.co.il/blogs/guyt/archive/2008/03/22/windows-server-core-coreconfigurator-to-the-rescue.aspx or here http://www.codeplex.com/CoreConfig Step 2: Application Server hosting set-up With the upper tool you can install the features of Windows Core (IIS 7) and its components, but for configuration we are back again to command line, using : AppCmd.exe – here is the way to use it to set up IIS web server http://learn.iis.net/page.aspx/114/getting-started-with-appcmdexe/ Now comes the funny part – Installing .NET framework 2.0 and 3.5 on Windows Core. follow up in part 2 of this post full installation guide : http://technet.microsoft.com/en-us/library/cc753802.aspx

[cosmin dumitru] Windows 7 Beta in VirtualBox

cosmin dumitru — Sat, 03 Jan 2009 13:46:44 GMT

In the Holiday times i try the brand new Win 7 Beta 1 - 7000.0.081212-1400_client_en-us_Ultimate-GB1CULFRE_EN_DVD.ISO and for sure that i want that virtualized, so i use for some time the Sun VirtualBox to host my virtualized development environment. In the new Beta 1 are many fixes, features and updates of the previous version from PDC2008, look to entire list here: http://windowsteamblog.com/ on installing virtual machine additions i got the message "This Operating system is not yet supported.“ but just using simple Device Manager , driver update lookup to M additions folder i was able to use the Network card and extended video adapter. Btw. Windows 7 developer guide it is also released http://code.msdn.microsoft.com/Win7DeveloperGuide cool things inside, Windows Biometric Framework (WBF) and Direct3D 10.1 Command Remoting and many others cool new stuff.