Howdy!
The certificate is actually $99, if you click through to Verisign
via WinQual. (Or click the link below.)
https://securitycenter.verisign.com/celp/enroll/upsell?promo_code=THEDEAL99&application_locale=VRSN_US&originator=VeriSign:CELP&bundle_id=MSIECS002&enable_option
Installing is okay, I suppose, but enabling by default?! Yikes.
/rafael
On 10/6/2010 8:45 PM, Nasser Dassi wrote:
Bloody. This just in from ScottGu.
NuPack Integration: ASP.NET MVC
3 automatically installs and enables NuPack as part of its
Yep, agreed. My Hello World app can print that xml out too.
/rafael
On 9/11/2010 12:33 AM, Nasser Dassi wrote:
Ahem. That's not proof that you're NOT crazy. That's
just proof that WinSxS binding policies is no lie. =)
- nasser
LONGLONG is merely __int64 in hiding. Careful though, it's __int64 on
all platforms, i.e. x86, x64, IA64.
/rafael
On 9/1/2010 12:17 PM, Elizabeth M Smith wrote:
> On 9/1/2010 12:16 PM, Olaf van der Spek wrote:
>> On Wed, Sep 1, 2010 at 3:53 PM, Philip Allison
>> wrote:
>>> Is __int64 the most
I noticed LP has code review capabilities built in. We should leverage
that! But it seems tied into branch merging, so I guess we'll need to
agree on some sort of branch structure, procedures, etc...
Anyone use this before?
/rafael
___
Mailing list: h
X64 code won't run on IA64 platforms. We're still supporting x86, x64
platforms though.
/rafael
On 8/20/2010 9:26 AM, Eric Schultz wrote:
> Wait now, what's going on with x64?
>
> On Fri, Aug 20, 2010 at 8:05 AM, Garrett Serack
> mailto:garre...@microsoft.com>> wrote:
>
> X86 packages *shoul
I've been pushing driver support a) because I'd personally like to
CoApp-ify Windows Sensors and b) to annoy Garrett. All binaries will be
signed, so devs will just need to make sure they're signed with one of
the few CAs supported by the Windows kernel.
/rafael
On 8/12/2010 11:00 PM, Jonathan W
@lists.launchpad.net]
> *On Behalf Of *Trevor Dennis
> *Sent:* Thursday, August 12, 2010 6:07 PM
> *To:* Rivera, Rafael
> *Cc:* coapp-developers@lists.launchpad.net
> *Subject:* Re: [Coapp-developers] Questions, Questions, Questions
>
>
>
>
>
> On Thu, Aug 1
the package name, version,
> architecture and the publisher's public key token, the same package
> will always have the same ID.
>
> Eric
>
> On Thu, Aug 12, 2010 at 7:43 PM, Rivera, Rafael
> mailto:raf...@withinwindows.com>> wrote:
>
> Maybe I missed
Maybe I missed something, but these IDs are globally unique. Why are we
hashing again?
/rafael
On 8/12/2010 8:39 PM, Eric Schultz wrote:
>
> I don't think we should call this a GUID if you're not using the
> official definition of a GUID/UUID from RFC 4122. If I see GUID
> in docume
It's as designed.
/rafael
On 8/11/2010 2:01 PM, Olaf van der Spek wrote:
> On Wed, Aug 11, 2010 at 7:59 PM, Garrett Serack
> wrote:
>
>> It's important to note that content outside the embedded CAB files are not
>> compressed (so any data/metadata in the MSI tables for example) and that
>>
That's a pretty poor reason to not type a few extra characters... but I
can't offer a concrete reason why we should support ANSI.
/rafael
On 8/4/2010 11:25 AM, Elizabeth M Smith wrote:
> On 8/4/2010 11:13 AM, Rivera, Rafael wrote:
>> Looks nice, love the chip name.
>>
On 8/4/2010 11:25 AM, Elizabeth M Smith wrote:
On 8/4/2010 11:13 AM, Rivera, Rafael wrote:
Looks nice, love the chip name.
Just one note -- I see wide-character strings in use. I suggest
replacing them, and their print functions, with T equivalents, leaving
the
And waste two bytes?! Silly ANSI and ISO C standards.
/rafael
On 8/4/2010 10:30 AM, Olaf van der Spek wrote:
>
>> '\\ No newline at end of file'
>>
> Might be a good idea to add this newline to every file. A shame VS
> doesn't do this by default...
>
_
Looks nice, love the chip name.
Just one note -- I see wide-character strings in use. I suggest
replacing them, and their print functions, with T equivalents, leaving
the choice of ANSI or UNICODE to the magical defines in the headers and
ultimately the human compiling this stuff.
So, from initia
Request denied. "Get back to work, you slacker."
On 8/3/2010 12:46 PM, Garrett Serack wrote:
I need a bit of a summer break, I’ll be taking
off Wed thru Fri this week.
G
I think we can all agree that middle-posting is the future.
/rafael
On 7/27/2010 10:34 AM, Olaf van der Spek wrote:
> On Tue, Jul 27, 2010 at 4:29 PM, Trevor Dennis wrote:
>
>> Gmail, Thunderbird, etc, have top replying as well. It's just more natural
>> to read the reply rig
On 7/27/2010 10:25 AM, Olaf van der Spek wrote:
On Tue, Jul 27, 2010 at 4:11 PM, Garrett Serack wrote:
I know where the switch is… What’s wrong with HTML emails?
There's no need for it and together with top and Outlook's quoting
style it's annoying.
Olaf
I've had success with branding via 99designs.com, uses a submission/vote
system and yields very high quality work. Just an alternative if you need.
/rafael
On 7/19/2010 6:53 PM, Garrett Serack wrote:
>
> I think we're going to need some visual identity for CoApp.
>
>
>
> I'd like to hold an ico
WONTFIX
On 7/14/2010 10:12 AM, Garrett Serack wrote:
https://bugs.launchpad.net/tortoisebzr/+bug/497312
Garrett
Serack
Yeah, they're called 'extensions'.
http://visualstudiogallery.msdn.microsoft.com/en-us/
/rafael
On 7/11/2010 3:42 PM, Adam Baxter wrote:
> Are these distinct from addons?
>
> --Adam
>
> ___
> Mailing list: https://launchpad.net/~coapp-developers
> Post
Hi Laura,
Regarding #2: This came up during the summit and we all agreed there
would be a "portable" installation flag/command. This would allow you to
deploy an application to a custom location, like a USB flash memory.
Surprise! :)
/rafael
On 6/28/2010 7:11 PM, m...@distasis.com wrote
> Second
Our Freenode operator friend mgdm has pushed our IRC channel (#coapp)
paperwork through and we can now register shiny /cloaks/. Cloaks are
just strings of text that replace your hostname/IP information on the
IRC network. In our case, we were given the /coapp/ namespace. The
format we must follow i
Ditto!
/rafael
On 6/9/2010 2:07 PM, Elizabeth M Smith wrote:
> On 6/9/2010 2:05 PM, Philip Allison wrote:
>> I'm not Elizabeth, but since there was no reply (at least not that I
>> can see), I'll bite. Basically, there are only two (sensible) ways
>> to do it: callbacks, or a "get current status
Ahh my ears are burning. /splashes gasoline
CoApp can definitely be used to deploy (both user-mode and kernel-mode)
device drivers. There's a blueprint for this package type on the wiki,
but hasn't been fleshed out yet
(http://coapp.org/Blueprints/Package_Blueprint/Role%3a_Device_Drive
I ran them through the automatic fixing widget in WLPG in the interest
of time, so YMMV.
http://www.flickr.com/photos/rafaelrivera/sets/72157624065606087/
/rafael
On 6/2/2010 1:44 PM, Garrett Serack wrote:
> Thanks, these help a lot.
>
> Does anyone else have any?
>
>
> Garrett Serack | Open Sour
I do. Let me get them onto Flickr.
/rafael
On 6/2/2010 1:44 PM, Garrett Serack wrote:
> Thanks, these help a lot.
>
> Does anyone else have any?
>
>
> Garrett Serack | Open Source Software Developer | Microsoft Corporation
> I don't make the software you use; I make the software you use better o
"Microsoft Visual C++"
/rafael
On 5/20/2010 4:35 PM, Rivera, Rafael wrote:
> Two issues come to mind immediately:
>
> * Servicing: If Microsoft pushes out a QFE for some CRT vulnerability
> (http://is.gd/chWRN), users will be stuck with a vulnerable CoApp engine
> until
eful with regards to memory management.
(e.g. don't xalloc() memory in one and xfree() in another).
/rafael
On 5/20/2010 4:16 PM, Olaf van der Spek wrote:
> On Thu, May 20, 2010 at 10:14 PM, Rivera, Rafael
> wrote:
>
>> On 5/20/2010 4:03 PM, Trent Nelson wrote:
>>
On 5/20/2010 4:03 PM, Trent Nelson wrote:
> I'm perplexed why anyone would want to forgo the advantages of C++ for
> C; I can make my C++ DLLs just as small as C ones. And, like, what if
> I want a linked list, or a hash, or a set, are we planning on writing
> all of those from scratch? Even stri
[Microsoft Detours 2.x Professional] - [Important]
Provides x64 support.
/rafael
On 5/20/2010 12:25 PM, Garrett Serack wrote:
Hey folks,
I’m trying to prioritize all the crap on my
plate, and I don’t want to drop anything so I need everyone who is
blocking on something
Using SQL Server will also allow us to port easily to SQL Azure (cloud
computing) when needed.
/rafael
On 5/20/2010 12:41 PM, Roberto Carlos González Flores wrote:
> +1 to SQL Server, I love the elegancy of PostgreSQL and I recognize
> that PostreSQL is faster than SQL Server, but we are inside a
Boogers.
___
Mailing list: https://launchpad.net/~coapp-developers
Post to : coapp-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~coapp-developers
More help : https://help.launchpad.net/ListHelp
te:
> On 5/18/2010 3:32 PM, Rivera, Rafael wrote:
>
>> Sadly, some of OpenSSL's assembly implementations are inline hacks (e.g.
>> bignum). This is going to be a pain to port to x64... using Microsoft's
>> compilers.
>>
> The x86_64 work is alrea
Sadly, some of OpenSSL's assembly implementations are inline hacks (e.g.
bignum). This is going to be a pain to port to x64... using Microsoft's
compilers.
/rafael
On 5/18/2010 4:24 PM, William A. Rowe Jr. wrote:
> On 5/18/2010 2:57 PM, Elizabeth M Smith wrote:
>
>> I'm not writing assembly -
Good idea, was playing with some PXE boot code today. coapp-pxe? [evil
grin]
/rafael
On 5/18/2010 1:08 PM, Garrett Serack wrote:
FYI:
I’ve requested the CoApp project be renamed to
CoApp-Engine, and we’re creating a CoApp project group which all our
new projects can be c
Hey Olaf,
Glad to hear you made it home in time! I think last we all spoke, we
needed a license before code could be committed. I'm sure that's on
Garrett's long TODO list.
/rafael
On 5/17/2010 5:54 PM, Olaf van der Spek wrote:
> Hey,
>
> Did everybody have a good flight? Turns out I was back ju
Visual Studio also has code from PreEmptive that lets you instrument
compiled applications, similar to Microsoft's own SQM/CEIP. Perhaps we
could tie into that one day.
/rafael
On 5/6/2010 12:18 PM, Garrett Serack wrote:
>
> I think this is a good idea. Definitely something we'll have to look
> a
There are also fully functional 30/90/180+ day trials freely
downloadable. No excuse really.
/rafael
On 5/6/2010 11:56 AM, Tom Hanrahan wrote:
>
> A *nix utility may be a good idea anyway, but we have programs in
> place for developers who need/want a copy of Windows for their test
> and developm
+1 for boost
openssl
vlc
detours
sally's xxx game collection
/rafael
On 5/5/2010 11:45 AM, Olaf van der Spek wrote:
Libs: bzip2, z, jpeg, png, ogg, vorbis,
boost, DX SDK, Windows SDK.
On Wed, May 5, 2010 at 4:59 PM, Garrett Serack
wrote:
Hey Garrett, -
Can you prep. like a CoApp 101 for a refresher in the morning? It may be
awfully boring, but I think it's good to solidify the foundation before
building on top of it :)
/rafael
On 4/22/2010 11:09 AM, Garrett Serack wrote:
>
> Rest assured, absolutely everything will be published.
Now you've done pissed off Thunderbird. It thinks your last email was a
scam. Personally, I'm on the fence.
/rafael
On 4/22/2010 6:46 PM, Garrett Serack wrote:
>
> LOL
>
>
>
> Well, I was thinking XML as a validate-able data format. I didn't
> actually have a plan. .INI file?
>
>
>
> I'd lik
Don't forget to raid the various team closets for swag!
/rafael
On 4/20/2010 6:06 PM, Garrett Serack wrote:
Howdy ya’ll,
I’m putting together a two day CoApp Design and
Development summit here on the Microsoft Campus.
It’s going to be two days of fleshing out the
d
Anyone can push malware through Windows Update with little effort.
Microsoft doesn't perform a useful security audit of published binaries;
they simply rely on the fact that signing requires a slew of IDs and
secret handshakes which are difficult to fake (i.e. remain an anonymous
baddie).
I think
I'm EST (GMT-5). After COB hours are best (530pm-midnight+).
/rafael
On 4/15/2010 7:31 PM, Garrett Serack wrote:
> I’d like to set up a time we can have a presentation and conference call
> so people have an opportunity to ask some questions, and perhaps get
> introduced to the larger vision that
On the "What is CoApp?" page, one of CoApp's "will" bullets mentions use
of Profile Guided Optimization (PGO). I'm curious as to how CoApp will
provide PGO capabilities given we (licensed Visual Studio users) had to
pay for it. PGO isn't available in Visual Studio Express SKUS.
Perhaps this is a V
That sounds more manageable and useful than simply logging the chan 24/7.
/rafael
On 4/9/2010 2:38 AM, Adam Baxter wrote:
> Furthermore, what I have seen other projects do is call an IRC meeting,
> which is then logged manually. That way project related discussions can
> be more easily used as th
Sorry, I was too quick to reply. I understand you can run both side by
side, which is cool.
Just wanted to add some tiny print that said "reparse aware" next to
your use of "application". Swapping of links creates a disaster for
normal applications that load bits from their directory at runtime.
Hmm, do you have a scenario that benefits from this? I'd still have to
kill the old application to launch the updated one...
/rafael
On 4/7/2010 2:36 PM, Garrett Serack wrote:
> So it turns out that option #1 has another benefit.
>
> ** You can delete and recreate the symlink without having to s
ft Corporation
> I don't make the software you use; I make the software you use better on
> Windows.
>
> From: coapp-developers-bounces+garretts=microsoft@lists.launchpad.net
> [mailto:coapp-developers-bounces+garretts=microsoft@lists.launchpad.net]
> On Behalf Of River
.net
> [mailto:coapp-developers-bounces+trevor=dennis-it@lists.launchpad.net]
> On Behalf Of Garrett Serack
> Sent: Wednesday, April 07, 2010 10:22 AM
> To: Rivera, Rafael; coapp-developers@lists.launchpad.net
> Subject: Re: [Coapp-developers] Another kind of package
>
>
I'm new to the conversation, so I don't have quoted material -- apologies.
*Program Files\ hosting*
Starting with Windows Vista and Windows Server 2008, we have
virtualization that silently takes over and redirects (for appcompat
reasons) writes to the caller's virtual application store. With W
Thanks for the reply Bob. It appears that neither DIFx or DPInst support
the Sensor driver type. SetupAPI appears to work just fine, installing
the sensor as a "legacy" driver -- funny yet sad.
/rafael
On 2/26/2010 11:32 AM, Bob Arnson wrote:
> On 2/24/2010 10:33 AM, Rivera,
Howdy.
I put together a WiX 3.0 package, utilizing the DIFx extensions, to
install a Windows 7 Sensor (UMDF driver). During installation, DIFXAPP
logged "No matching devices found in INF" and simply threw the driver
into storage. I read I'm to populate my INF with an appropriate
DriverPackageT
54 matches
Mail list logo